Rfid drive management facility

ABSTRACT

In embodiments of the present invention improved capabilities are described for managing RFID tags, where an RFID tag and associated RFID tag data are presented to a computing device through an RFID drive management facility as a seamless extension of a logical file system within the computing device such that the RFID tag and associated RFID tag data can be managed in a manner that is consistent with other items within the file system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of the following provisionalapplication, which is hereby incorporated by reference in its entirety:U.S. App. No. 61/556,359, filed on Nov. 7, 2011.

This application is a continuation-in-part of U.S. patent applicationU.S. application Ser. No. 12/629,955, filed Dec. 3, 2009, which isincorporated by reference in its entirety, and which is acontinuation-in-part of U.S. patent application Ser. No. 12/393,863,filed Feb. 26, 2009, which is incorporated by reference in its entirety.

The U.S. application Ser. No. 12/692,955 claims the benefit of thefollowing provisional applications, each of which is incorporated byreference in its entirety: U.S. patent application 61/182,776 filed Jun.1, 2009; and 61/238,430 filed Aug. 31, 2009.

The U.S. application Ser. No. 12/393,863 is a continuation-in-part ofU.S. patent application Ser. No. 11/926,033 filed Oct. 28, 2007, andU.S. patent application Ser. No. 11/609,277, filed Dec. 11, 2006, eachof which is incorporated by reference in its entirety.

The U.S. application Ser. No. 12/393,863 claims the benefit of thefollowing provisional applications, each of which is incorporated byreference in its entirety: U.S. patent application 61/031,590 filed Feb.26, 2008; and U.S. patent application 61/119,595 filed Dec. 3, 2008.

The U.S. application Ser. No. 11/926,033 claims the benefit of theprovisional application 60/915,838 filed May 3, 2007, and isincorporated by reference in its entirety.

The U.S. application Ser. No. 11/609,277 claims the benefit of thefollowing provisional applications, each of which is incorporated byreference in its entirety: U.S. patent application 60/868,107 filed Dec.1, 2006; U.S. patent application 60/803,612 filed May 31, 2006; U.S.patent application 60/803,610 filed May 31, 2006; and U.S. patentapplication 60/749,645 filed Dec. 9, 2005.

BACKGROUND

1. Field

This invention relates to Radio Frequency Identification (RFID) tags,and more specifically to methods of reading RFID tags.

2. Description of the Related Art

Conventionally, standard software, whether office, business, enterpriseor of other type, is not capable of interacting with RFID tags. Instead,special applications are written, either as self-contained applicationsthat read and write data to tags (sometimes called edgeware) or by usingso called middleware that can connect tags in a database or eventformat. Thus only individuals with special software are able to exchangedata with an RFID tag.

When deploying a solution based on high memory tags, specific items maybe defined which must be at specific memory locations, for example asdefined in the EPCglobal tag data standards. Some higher-levelstandards, such as the ATA Spec 2000, also define memory usage in thismanner, and postulate a programmer API such that records may be storedand retrieved in a manner reminiscent of conventional database usage.Therefore, the tag is treated as a new and distinct part of the system,requiring a unique method of interacting with it, and special purposesoftware, whether edgeware or middleware, to handle tag data as words,objects or data records in order to use the tags.

As RFID tags have become more widely used, there has emerged a need foreasier means of accessing and storing information on RFID tags thatavoids the need to develop and integrate custom applications.

SUMMARY

Disclosed herein include embodiments that enable a user to exchange datawith an RFID tag through an RFID drive management facility as a seamlessextension of a filing system within a computing device such that theRFID tag and associated RFID tag data may be managed in a manner that islogically consistent with other items within the file system, where thecomputing device may be a server, desktop computer, laptop computer,smart phone, and the like. For instance, the RFID tag may appear to acomputer in a similar way as a file folder or flash drive would appear,where the user is able to move data to and from the RFID file systemelement through drop-and-drag actions, and where the RFID drivemanagement facility is transparent to the user.

These and other systems, methods, objects, features, and advantages ofthe present invention will be apparent to those skilled in the art fromthe following detailed description of the preferred embodiment and thedrawings. All documents mentioned herein are hereby incorporated intheir entirety by reference.

BRIEF DESCRIPTION OF THE FIGURES

The invention and the following detailed description of certainembodiments thereof may be understood by reference to the followingfigures:

FIG. 1 shows a schematic of the RFID tag system and associated systems.

FIG. 1A shows a block diagram embodiment showing major components of anRFID tag.

FIG. 1B shows an embodiment of storing information within OTP memoryusing a segment table and data maps is shown.

FIG. 1C shows a flow chart embodiment of a write algorithm that mayallow for recovery from a low or no power situation during a writeoperation.

FIG. 2 shows a schematic of the overall RFID tag communication system.

FIG. 3 shows a block diagram schematic of an RF network node.

FIG. 4 shows a schematic flow chart of a typical communication between areader and an RFID tag.

FIG. 5A shows an embodiment of the electrical reference groundinterconnection configuration.

FIG. 5B shows an embodiment of inter-RF network node communication.

FIG. 5C shows a system for determining a master RFID network nodes amonga plurality of RFID network nodes.

FIG. 6 is a schematic diagram for a circuit associated with an RFID tagsystem.

FIG. 7 shows an embodiment of a communication signal for determinationof a master RF network node.

FIG. 8 shows an embodiment of the communication protocol for master nodecommunication collisions.

FIG. 9 shows a schematic of an improved RFID tag system.

FIG. 9AA shows an embodiment of how RFID tags may be connected toantennas in a series configuration via a super strap.

FIG. 9AB shows an embodiment of how RFID tags may be connected toantennas in a parallel configuration via a super strap.

FIG. 9AC shows an embodiment of how RFID tags may be connected toantennas in a series-parallel configuration via a super strap.

FIG. 10 shows a method of establishing redundancy in an RFID tag system.

FIG. 11 shows a range of embodiments of RFID tag systems with sensorcapabilities.

FIG. 12 shows an embodiment of a screen printing method for an RFID tagsystem.

FIG. 13 shows an embodiment of forcing an RF network node to asubstrate.

FIG. 14 shows orientation of components in an embodiment of a screencoating application in an RFID tag system.

FIG. 15 shows an embodiment of a thermal printer ribbon 1202 applyingink, wax, resin, or the like to a substrate.

FIG. 16 shows a vacuum attachment method for an RFID tag system.

FIG. 17 shows the systems associated with a reader.

FIG. 18 shows components of a method for facilitating increased memoryin an RFID tag system.

FIG. 19 shows a method of facilitating communication among chips on anRFID tag.

FIG. 20 shows a method of impedance matching for an RFID tag system.

FIG. 21 shows a range of applications enabled by an RFID tag system.

FIG. 22 shows a range of applications enabled by an RFID tag system in acommercial environment.

FIG. 23 shows a range of applications enabled by an RFID tag system inan industrial environment.

FIG. 24 shows a range of applications enabled by an RFID tag system in aconsumer environment.

FIG. 25 shows a range of applications enabled by an RFID tag system in agovernment environment.

FIG. 26 shows a range of applications enabled by an RFID tag system inan agriculture environment.

FIG. 27 shows a range of applications enabled by an RFID tag system in amilitary environment.

FIG. 28 shows a range of applications enabled by an RFID tag system in amedical environment.

FIG. 29 depicts an embodiment for the programming of a compositemulti-tag facility.

FIG. 30 depicts an embodiment of a composite multi-tag facility.

FIG. 31 depicts an embodiment functional block diagram of the RFID drivemanagement facility interfacing with a file system of a computer device.

FIG. 32 depicts an embodiment functional block diagram of the RFID drivemanagement facility interfacing with a computer device across a network.

DETAILED DESCRIPTION

In aspects of the systems and methods described herein, a radiofrequency identification (RFID) tag may use multiple RF network nodes(e.g. radio microchips) to communicate information to a RFID reader, anetwork, other RFID network nodes, or the like. The communication of theinformation may be provided to the RFID reader using at least oneantenna, using a communication facility, using both the at least oneantenna and the communication facility, or the like.

In aspects of the systems and methods described herein, each of themultiple RF network nodes may include radio frequency circuits, digitalcircuits, memory storage, communication facilities, and the like forstoring and transmitting information to RFID readers, networks, otherRFID tags, markets, applications, data stores, and the like. The RFIDtag may include circuitry for inter RF network node communication thatmay provide RF network node redundancy, increased functionality,improved connectivity to the reader, increased RFID tag memory, RFID tagmemory management, and the like.

In embodiments, the RF network node redundancy may provide for a morerobust RFID tag that may provide greater resistance to damage, greatercapability to work in harsh environments, functionality and memory whendamaged, or the like. RF network node redundancy may support a protocolof one RF network node providing a backup to another RF network node.For example, if one RF network node is damaged, another RF network nodemay assume the role of the damaged RF network node.

In embodiments, the increase RFID tag functionality may be provided bythe inter RF network node communication. On the multiple RF network nodeRFID tag, the different RF network nodes may provide differentfunctionality to the RFID tag. For example, one of the RF network nodesmay provide memory management while another RF network node may provideencryption capabilities. In an embodiment, there may be a master RFnetwork node that may coordinate the capabilities that the different RFnetwork nodes may provide.

Aspects of the systems and methods described herein may provide forimproved connectivity with the RFID reader. By using multiple antennasand multiple RF network nodes, the RFID tag may be able to communicateusing different frequencies, may be able to adjust the impedance of theRF network node for an improved signal quality, may have an increasedrange of transmission, or the like. By communicating with multiplefrequencies, the RFID tag may be able to select a frequency thatprovides an advantageous transmission characteristic for differentenvironments such as liquids and metals. The RFID tag may be able toselect one of the available antennas that may provide the best impedancematch to the RFID tag and RF network nodes. The impedance match mayprovide a clearer transmission signal from the RFID tag to the RFIDreader.

In an embodiment, the multiple RF network node RFID tag reflecting orbroadcasting at the same time may improve the signal strength. Theimproved signal strength may increase the RF amplitude that may increasethe range of the RF signal. The increased signal strength may beparticularly advantageous when the tag is applied to an item thatcontains a liquid. The liquid may absorb radio waves, and the increasedsignal strength may allow the signal to reflect or broadcast fartherdespite the presence of a liquid.

In an embodiment, the multiple RF network node RFID tag reflecting orbroadcasting together may improve the signal clarity. The simultaneousreflecting or broadcasting of a plurality of RF network nodes mayprovide a more rapid RF transition similar to a square wave. The rapidRF transition may allow the signal to be received faster by the reader.In an embodiment, less expensive readers may be used because the RFsignal may be clearer. In an embodiment, the clearer signal may beimportant when the RFID tag is on a metal object that tends to reflectthe RF signal.

Aspects of the systems and methods described herein may provide forincreased memory for the RFID tag. Using the inter RF network nodeconnectivity, the memory for the multiple RF network nodes may bemanaged to provide expanded memory, redundant memory, distributedmemory, or the like. For example, if each of four RF network nodes has 8Kb of memory, the memory of all four RF network nodes may be combined toprovide a total memory for the RFID tag of 32 Kb. In another example,the four RF network nodes may provide redundant memory where all four ofthe RF network nodes store the same information.

Aspects of the systems and methods described herein may provide forinterfacing with external sensors. The sensors may provide informationsuch as temperature, humidity, acceleration, gas levels, smoke, heat, orthe like. The RFID tag may read the sensors and the information may besaved to the RFID tag, the RFID tag may provide the stored sensorinformation to the reader on the next read request. The sensorinformation may be used by the RFID tag to calculate freshness of aproduct, the environment in which a product is stored, the handlinghistory of a product, or the like.

Aspects of the systems and methods described herein may provide forinter-RFID tag communication using a communication facility that mayinclude a gateway facility. Using the gateway facility, the RFID tag maybe able to communicate to a network, to other network capable devices,to other network capable RFID tags, or the like. The inter-RFID tagcommunication may allow the RFID tags to provide redundant informationbetween RFID tags. Additionally, the RFID tags may be able tocommunicate information from one RFID tag to another RFID tag to form atag network that may be similar to a mesh network where information maybe transmitted using a number of different routes.

In an embodiment, the cost of producing the RFID tag 100 may be reducedbecause the RF network node may not require precise placement on anantenna lead. Placement machinery may be expensive and the placementsequence may be time-consuming, both of which may result in increasedRFID tag cost. The RF network nodes as described herein may be randomlyplaced on the antenna lead.

In an embodiment, smaller RF network nodes may be used becausenon-precise placement is more easily performed. Smaller RF network nodesmay be less expensive. By contrast, machinery used at present to placeRF network nodes may not be able to place the smallest available RFnetwork nodes.

The increased capabilities of the multiple RF network node RFID tag mayprovide increased capabilities for markets to track materials, trackproducts, track employees, track patients, provide security, and thelike. For example, the increased memory capabilities of the multiple RFnetwork node RFID tag may allow for the storage of tracking informationthrough a distribution system. At each point in the distribution systemthe RFID tag may receive and transmit information to and from thereader.

In another market example, the increased RFID tag memory may allow thestorage of patient information that may be read to determine if thepatient is to receive a certain medicine. The RFID tag may containenough increased memory to store all of the patient's medicineinformation, surgical history, medical history, and the like that mayaid in the proper administering of medications. For example, a nurse mayuse a portable reader to read the patient information and medicineinformation to assure that the medicine is appropriate for the patient.

In another example, the multiple RF network node RFID tags may storesecurity information that may determine if a person may enter a room,building, facility, or the like. The RFID tag may store personalinformation, security access information, record location information totrack the movements of the person within a facility, or the like.Throughout this disclosure the phrase “such as” means “such as andwithout limitation”. Throughout this disclosure the phrase “for example”means “for example and without limitation”.

Referring to FIG. 1, an embodiment of the RFID tag 102 and associatedinterfaces, facilities, markets, and applications is shown. Features ofthe depicted embodiment are directed to optimizing certain interfacesthat are shown in FIG. 1. As would be understood in the art, forexample, an interface between an antenna 108 and an RF network node 104may be susceptible to electrostatic discharge (ESD), a sudden andmomentary electric current that may flow when an excess of electriccharge finds a path to an object at a different electrical potential,such as ground, power, or the like. The term may often be used inelectronics and other industries to describe momentary unwanted currentsthat may cause damage to electronic equipment. The antenna 108 may be asource of such accumulated charge, which may lead to electrostaticdischarge into the electronics of a RFID tag 102. In embodiments, theremay be an ESD and impedance matching 110 components as a part of a RFand Analog block 302 that reduce the accumulation of charge that maylead to ESD, reduce the effects of ESD, protect against ESD, or thelike.

It would be further understood in the art, as another example, that theinterface between the antenna 108 and the RF network node 104 may besusceptible to impedance mismatch due to changes in the antenna 108configurations, changes in the environment, changes in electricalproperties of components, or the like. Impedance matching may attempt tomake the output impedance of a source, the antenna 108 for instance,equal to the input impedance of the load to which it is ultimatelyconnected, the input to the RF network node 104 for instance. Impedancematching is usually implemented in order to maximize the power transferand minimize reflections from the load. The concept of impedancematching may be applied when energy is transferred between a source anda load. Sometimes the term “impedance matching” may be used moregenerally to mean “choosing impedances that work well together” insteadof “making two impedances complex conjugate”. The more generalinterpretation includes impedance bridging, where the load impedance maybe much larger than the source impedance. Bridging connections may beused to maximize the voltage transfer, rather than the power transfer.

In embodiments, the RF network node 104 may contain the ESD andimpedance matching 110 functional block. The ESD and impedance matching110 functional block may include multiple switch elements to connect ordisconnect impedance components such as capacitors, inductors,resisters, and combinations thereof. State control of these switches maydetermine the impedance match between the antenna 108 and the RF networknode 104. The setting of these switches may be controlled by analog ordigital circuit configurations. In embodiments, impedance matchingcontrol may be performed automatically to tune the impedance match byanalog circuitry upon reception of a carrier wave, with impedancematching implemented in the RF and analog block 302 of the RF networknode 104. The impedance match from tuning the impedance matching mayincrease the power level received from the antenna. In embodiments,there may be too much power being delivered to the RF network node 104,and the circuit may need to be de-tuned (mismatched impedance) to reducethe received power. Detuning may be performed if voltages exceed theoperating supply voltage, to ensure that circuitry connected to thesupply derived from the RF power is not damaged. In an embodiment, thedetuning mechanism may serve as a voltage limiter to the RF network node104 circuitry. In embodiments, control of the impedance matching in theESD and impedance matching 110 functional block may provide a way toincrease received power by tuning to improve the impedance match, orprotecting the circuitry on the RF network node 104 from high inputvoltages by detuning the impedance match.

In embodiments, impedance matching may be controlled digitally bycombinatorial logic, sequential logic, a program subroutine, or the likeand may be implemented after the power to the RF network node 104 hasstabilized and a data processing and controller block 132 has beenpowered up. The digital control for impedance matching may be alterablethough programming internal to the RF network node 104, or externallythrough read/write capabilities of the RF network node 104. Digitalcontrol is described in more detail below.

In embodiments, implementation of impedance matching between the antenna108 and the RF network node 104 may provide a way to automaticallyadjust to initial conditions upon power up due to a received modulatedcarrier from a reader 140. This automatic adjustment to impedancematching may improve the chances for the RFID tag 102 to communicatewith the reader 140 when distance, environment, materials, or the like,would otherwise limit the initiation of such communication. Inembodiments, implementation of impedance matching between the antenna108 and the RF network node 104 may provide a way to systematicallyadjust impedance matching to maintain maximum received power or voltage.This systematic adjustment may allow for compensation from impedancemismatches resulting from changes in environment, such as moisture,proximate conductors such as metals or liquids, or the like. The abilityof the RFID tag 102 to adjust impedance matching may allow the RFID tag102 to operate more reliably under changing environmental and productusage conditions.

Another embodiment of impedance matching may be dynamic impedancematching. Dynamic impedance matching may include adjusting the centerfrequency sent by the reader and received by the RFID tag 102,dynamically adjusting the capacitance of the RFID tag 102 to match theimpedance of the of the object to which the RFID tag 102 is attached, tomatch the impedance of the environment where the RFID tag 102 may beoperating, or the like. Depending on the type of object on which theRFID tag 102 is attached (e.g. water or metal) or the operatingconditions, different center frequencies may perform better then others.For example, in the US, the RFID tag center frequency may be 915 MHZ,but if the RFID tag 102 is attached to a case of water, the RFID tag 102communication may be improved using a different center frequency.

In an embodiment, the center frequency may be determined by programmabletuning of the RFID tag 102 center frequency. Programmable tuning of theRFID tag 102 center frequency may be accomplished by a user transmittinga digital word from a reader 140 that represents the new frequency withwhich the reader 140 and RFID tag 102 combination will communicate. TheRFID tag 102 may receive the digital word and may change the centerfrequency with which the RFID tag 102 may receive reader signals. In anembodiment, the digital word may be modified by the reader 140 and/orthe RFID tag 102 until a center frequency is established that providesfor the optimum communication frequency. In an embodiment, the centerfrequency digital word may be initiated by a user using a reader 140interface. The user may initiate the center frequency digital word basedon the object on which the RFID tag 102 is attached, based on theenvironment in which the RFID tag 102 is operating, or the like.

In an embodiment, the programmable tuning of the frequency may becombined with an RFID tag 102 power meter (e.g. the power meter isdescribed in more detail herein) to determine the optimum centerfrequency. For example, the user may transmit a digital wordrepresenting a starting center frequency. The RFID tag 102 may adjustthe receiving center frequency and the power meter may measure the powerdifference between the original center frequency and the new centerfrequency based on the received digital word. The power meter readingsmay be compared and a new frequency digital word may be determined basedon the change in the RFID tag 1021 received signal strength. In anembodiment, the reader 140 and RFID tag 102 may continue the adjustingof the center frequency until the optimum center frequency isdetermined. As may be understood, the center frequency adjustmentprocess may be used to adjust to the optimum center frequency for theobject on which the RFID tag is attached.

In an embodiment, in coordination to optimizing the center frequency,the impedance match of the RFID tag 102 to the antenna may bedynamically adjusted using a bank of variable capacitors (varactor). Inan embodiment, the dynamic impedance adjustment may be performedseparately from the center frequency optimization, in parallel with thecenter frequency optimization, in series with the center frequencyoptimization, in response to a request from the reader 140, in requestfrom the RFID tag 102, or the like. In an embodiment, the varactorcapacitance may be adjusted based on a voltage: in the case of the RFIDtag 102 the voltage may be an actual voltage measured by the powermeter, a power meter predicted voltage, or the like.

As one example of dynamic impedance matching, a digital wordrepresenting a new center frequency may be sent by the reader 140, thedigital word may have been determined by a user. The RFID tag 102 mayreceive the digital word and may use the word to adjust the centerfrequency used by the RFID tag. The power meter may measure the changein the received signal strength and may adjust the impedance match withthe antenna 108 by adjusting the varactors. Once the impedance has beenadjusted, the power meter may again measure the received signal strengthand a new digital word may be determined to again adjust the centerfrequency to optimize the received signal strength. This sequence ofadjusting the digital word, adjusting the impedance with varactors, anddetermining a new digital word may continue until an optimum centerfrequency is determined. It should be understood that there may be manydifferent sequence processes for dynamically adjusting the impedanceusing the digital word and varactors and this example is used forillustration purposes only and should not be considered as the onlymethod of optimizing the center frequency.

In embodiments, the RF network node 104 may contain a voltage limiterand multiplier 112 functions that boost the voltage of the incomingmodulated carrier, while limiting the voltage of the boosted signal to apredetermined maximum value. The voltage limiter and multiplier 112function may include a pre-multiplier stage, an intra-multiplier, an RFpower limiter, a voltage limiter, a current limiter, an over-voltagelimiter, and the like. The boost in the voltage may be a multiplyingfactor, such as times three, times five, times eight, or the like. Inembodiments, the output of the multiplier may produce voltages of 5volts or greater. Additionally, the operational circuitry of the RFnetwork node 104 may be of a technology that may be damaged if exposedto a voltage in excess of a specified maximum voltage, for instance 2volts. The voltage limiter may be required to limit the voltage to thiscircuitry to a voltage that is less than this specified maximum voltage,for instance 1.8 volts. In embodiments, the voltage limiter andmultiplier 112 may condition signals received from the ESD and impedancematching 110 circuitry, and may provide output to an envelope detectioncircuitry 114, as shown in FIG. 1.

FIG. 1 shows an embodiment of a boosted and limited modulated carrierpassing from the voltage limiter and multiplier 112, on to the envelopedetection 114 block and a demodulator 118 block. At the output of thevoltage limiter and multiplier 112, the signal's power may be boostedand limited, but still in the form of a modulated carrier. Inembodiments, the received modulated carrier may be amplitude-shift key(ASK) modulated, a form of modulation, which represents digital data asvariations in the amplitude of a carrier wave. In embodiments, thereceived modulated carrier may be single side-band (SSB), doubleside-band (DSB) ASK, Phase-Reversal Amplitude Shift Keying (PR-ASK), ormodulated by other modulation schemes, such as phase-shift keying (PSK),frequency-shift keying (FSK), quadrature amplitude modulation (QAM), orthe like.

The modulated carrier may require the envelope detection 114 prior todemodulation. In embodiments, the envelope detector 114 may be a simplesystem, such as a diode and a low-pass filter, or it may include a morecomplex circuit configuration. In addition, the envelope detection block114 may have a mean-detector, which detects the mean value of theenvelope and compares this output to the output of the envelope detector114 to determine whether the signal is a 1 or a 0. In embodiments, theenvelope detector 114 block may also provide other detection modes, forinstance, the envelope detector 114 block may provide for a synchronousdetection mode. Synchronous detectors may be considerably more complexthan envelope detectors. A synchronous detector may, for example,consist of a phase locked loop and multiplier circuits. In a synchronousdetector mode, multiplying the modulated carrier by a sine wave that isphase locked to the incoming carrier may be involved in thedemodulation. As shown in FIG. 1, however, the envelope detection 114functional block may represent any pre-demodulation technique, and isnot meant to be limited to any particular circuitry that may be referredto as envelope detection.

In FIG. 1, the demodulator 118 functional block may include thecircuitry for performing the final demodulation of the incomingmodulated carrier waveform received by the RF network node 104.Demodulation is the act of removing the modulation from the incominganalog signal. For instance, to demodulate an AM signal, the signal maybe passed through a diode rectifier. The amplitude variation may thenintegrate into the original modulating signal. Each modulation techniquerequires its own unique method for demodulation, and the demodulator 118shown in FIG. 1 is meant to represent the circuitry for the demodulationtechnique employed in certain embodiments. In embodiments, themodulation technique used in the demodulator 118 may be any modulationtechnique known to the art, such as ASK, PSK, FSK, QAM, or the like.

Certain embodiments may employ the ability to change the modulationtechnique as a way to improve system performance. For instance, thesystem may change the order of a QAM scheme in order to increase areception parameter, such as raising the QAM order to increase the bitrate when the RFID tag 102 is close to the reader 140, lowering the QAMorder to improve bit-error-rates when the RFID tag 102 is at anincreased distance from the reader 140, and the like. By accommodatingvarious modulation schemes, the RFID tag 102 may be able to improve itsdata rate and/or its operable range from the reader 140.

As shown in FIG. 1, the output of the demodulator 118 may then convertedto a digital signal and presented to the data processing and controller132 functional block for command processing, as discussed herein. Whencommand processing is complete, any required command response and/ordata return message to the reader 140 or the other RFID tags 102 may besent from the data processing and controller 132 to a modulator 128 forsignal conditioning prior to transmission. As in the case of thedemodulator 118, the modulator 128 may use a plurality of modulationschemes in communication with the reader 140 or the other RFID tags 102.In embodiments, the return modulation scheme may be PSK, a digitalmodulation scheme that conveys data by changing, or modulating, thephase of the carrier wave. The carrier wave for transmission of themodulated command response may be the backscattered carrier wavereceived from the reader 140. That is, the RFID tag 102 may not requirea carrier source generated within the RFID tag 102.

As shown in FIG. 1, the output of the modulator 128 may be sent to theESD and impedance matching 110 functional block. In addition to theimpedance matching performed between the antenna 108 and the RF networknode's 104 internal circuitry to improve transmission, the ESD andimpedance matching 110 block may provide a way of switching in animpedance element, such as a capacitor or inductor, in order topurposely provide impedance mismatching. This technique may beassociated with the modulation of the outgoing signal, and may beimplemented to change the imaginary part of the input impedance. PSK mayoffer the advantages of continuously available power with respect toASK. In embodiments, the modulation technique used in the modulator 128may be any modulation technique known to the art, such as ASK, PSK, FSK,QAM, or the like.

In addition to the antenna 108 to the demodulator 118 communicationpath, and the modulator 128 to the antenna 108 communications path withthe reader 140 and the other RFID tags 102, the RF network nodes 104 maycommunicate with each other through a common antenna connection 158. Tofacilitate this, a communications path between the data processing andcontroller 132 and the antenna(s) 108 may be implemented by way of aninter-node interface 154, as shown in FIG. 1. The inter-node interface154 may connect the data processing and controller 132 to the commonantenna connection 158 through the ESD and impedance matching 110 block.The connection of the inter-node interface 154 to the common antennaconnection 158 may be a direct connection or through circuit elementswithin the ESD and impedance matching 110 block.

In embodiments, the plurality of RF network nodes 104 connected togethervia the common antenna connection 158 may provide a distributedfunctionality for the RFID tag 102 with a master RF network node 104coordinating the functionality of the other RF network nodes 104 on theRFID tag 102. The distributed functionality may include combined memorylocations, separate multiple memory locations, secure memory locations,public memory locations, multiple frequencies, selective powerreduction, encryption, decryption, and the like. The interconnection ofdata processing and controller 132 blocks of the different RF networknodes 104 on the RFID tag 102 may significantly increase the overallfunctionality, flexibility, modularity, and/or redundancy of the RFIDtag 102.

In embodiments, the RFID tag 102 may operate as a device that ispassive, semi-passive, or active. These terms may refer to whether thereis a source of power internal to the RFID tag 102 or not. The passiveRFID tag 102 may not have an internal power supply. In the case of thepassive RFID tag 102, minute electrical currents induced in the antenna108 by the incoming radio frequency signal may provide just enough powerfor the RFID tag's 102 circuitry in the RFID tag 102 to power up andoperate. Therefore, the passive RFID tag 102 may not have a powersupply, but may still have a power management 130 block. FIG. 1 showsone embodiment of the interfaces between the power management 130 blockof the RF network node 104, and other function blocks within the RFnetwork node 104. Prior to any portion of the RF network node 104 beingpowered, the antenna 108 may receive the reader's 140 transmittedcarrier wave. This incoming signal may be fed to the power management130 block through the ESD and impedance matching 110 block in order toextract, or harvest, the power of the carrier wave. The power management130 block may then rectify and filter the incoming carrier wave toestablish a stable supply of power to the rest of the RF network node104. The power management 130 circuitry may be required to regulate theoutput voltage to the rest of the RF network node 104, which may varysignificantly depending on the EM field value of the received carrierwave.

In embodiments, the power management 130 may provide power to functionalblocks within the RF network node 104 at different times. For instance,power may be supplied to the RF and analog block 302 prior to powersupplied to the data processing and controller block 132, power may besupplied to a clock 120 prior to the rest of the RF and analog block302, power may be supplied for bias circuitry prior to controlcircuitry, and the like. In embodiments, power management 130 mayprovide logical signals to the RF network node 104 functional blocks toindicate the state of power readiness, such as a power-on reset (POR)signal, a power available signal, a power too low signal, and the like.These logical signals may better enable the proper power-up sequencewithin the RF network node 104. In addition, the power management 130control and status signals may allow for conservation of power duringthe RFID tag 102 operations in order to extend the operational time,increase the amount of circuitry powered in order to increase theavailable functionality of the RF network node 104, or the like. Thepower management 130 may include not only a means of harvesting powerfor use in the RF network node 104, but also provide logic and controlof power-up sequences and power conservation modes.

In embodiments, the multiple RF network nodes 104 on the RFID tag 102may share power. Shared power may provide for equal power distributedamongst the different RF network nodes 104, different power distributedamongst the different RF network nodes 104, control of the power used bythe different RF network nodes 104, or the like. In embodiments,distributed control of the power management 130 block may be implementedin a plurality of ways, such as the master RF network node 104controlling the power distribution amongst the different RF networknodes 104 of the RFID tag 102, the different network nodes 104 of theRFID tag 102 collectively monitoring and controlling power distribution,and the like. The algorithm for control of the distributed powermanagement 130 may be stored into the memory of the RF network nodes104. In embodiments, distributed control of power management 130 amongstthe different RF network nodes 104 of the RFID tag 102 may better enablethe RFID tag 102 to manage functional resources on the RFID tag 102.This may allow the RFID tag 102 to dynamically redirect the RFID tag's102 functionality to accommodate the changing demands from commandsreceived, market needs, redundancy management, link quality, or thelike.

Harvested power from the incoming carrier wave may drop below thethreshold power for a short time after the carrier wave from the reader140 has interrogated the tag. In an embodiment, the short period of timemay range from microseconds to seconds. During this transition toinsufficient power, the power management 130 block may communicate thisevent with a voltage too low signal. Information stored in volatilememory, and all volatile control states, may be lost after powertransitions below a minimum voltage. Certain information, stored inmemory or in control states, may be critical to future communicationsand operations. An example of such critical information may be thecontents of a flag register, indicating the operational or sequentialstates of an ongoing process or assignments. Power may terminate tooquickly for this information to be stored into non-volatile memorybefore power is lost. The systems and methods described herein mayprovide for a persistence 124 circuit that may enable selective memorycells to maintain their memory states for short periods in the absenceof power supplied by the incoming carrier wave. The short period forwhich memory states may be maintained may be 10 ms, 100 ms, 1 second, 5seconds, or the like. The memory cells that reside within thepersistence 124 circuit may function much like a capacitor, holding thecharge of the memory cell briefly, until stable power is re-established.In embodiments, the persistence 124 circuit may better allow the RFIDtags 102 to maintain continuity in operations and functionality in thepresence of brief disruptions of carrier wave transmission from thereader 140.

In an embodiment, the multi RF network node 104 RFID tag 102 may be ableto harvest power and backscatter information to the readersimultaneously. The RF network nodes 104 may coordinate thebackscattering of information to the reader and harvesting power byselecting at least one RF network node 104 to backscatter informationwhile at least one RF network node 104 harvest power from the incomingRF signal from the reader. For example, in a four RF network node 104RFID tag 102, one RF network node 104 may be selected to backscatter theinformation to the reader while three RF network nodes 104 harvest powerfrom the incoming RF signal. In an embodiment, the RF network nodes 104selected to backscatter or harvest power may be determined by theorientation of the RFID tag 102 to the reader. In an embodiment, the RFnetwork nodes 104 may coordinate which node will backscatter and whichnode will harvest power. Additionally, the RF network nodes 104 selectedto perform either backscattering or harvesting may differ for each RFIDtag 102 read. In this manner the RFID tag 102 may be able to harvest allthe available power from the incoming RF signal while alsobackscattering information to the reader. The result of the simultaneousbackscattering and power harvesting may be extended power and timeavailable to the RFID tag 102 for data computing, data storing, datatransmitting, and the like.

Depending on the reader signal strength, the amount of power harvestedby the RFID tag 102, the command transmitted by the reader, or the like,the power management 130 may schedule the power up of RF network nodes104 to receive power during a read cycle. By scheduling RF network nodes104, the power management 130 may power a RF network node, may not poweran RF network node, may power an RF network node for a short period, maypartly power an RF network node, or the like. For example, if the reader140 signal is weak and therefore less power is harvested, the powermanagement 130 may only power a portion of the RF network nodes. In anembodiment, the power management 130 may coordinate with the dataprocessing controller 132 to determine which RF network nodes 104 arerequired to provide a response and then may only power the required RFnetwork nodes 104. In another example, the command from the reader 140may not require all the RF network nodes 104 to complete a certain taskand the power management 130 may not power RF network nodes 104 that arenot required to complete the response to the reader. The result ofscheduling the RF network node power up may be to conserve the powerconsumed by the RFID tag 102 to allow for the required power and time tocomplete the reader 140 command.

In another embodiment, the RFID tag 102 RF network nodes 104 may sharethe harvested power. In an embodiment, the harvested power may be pooledin a power storage facility that may have a common connection betweenthe all the RF network nodes 104. In an embodiment, the power storagefacility may be a set of capacitors, a battery, a combination ofcapacitors and a battery, or the like that may be connected to thecommon connection, as power is harvested the power storage facility mayreceive and store the power. For power sharing, the individual RFnetwork nodes 104 may determine the amount of power required to executethe current reader command requirement and may share power received fromthe power storage facility with the other RF network nodes 104. Forexample, if the current command is a write operation and the RF networknode 104 memory is full, the RF network node 104 may determine that itcannot execute the write command and may share it's available power withthe other RF network nodes 104.

In an embodiment, the RF network node 104 power sharing may be a methodof the RF network node 104 determining that power is not required by theRF network node 104 and the RF network node 104 being isolated from thepower storage facility. In an embodiment, the sharing of power may beenabled by the setting of switches within the RF network node 104,setting switches within the power management 130, or the like, toisolate RF network nodes 104 from the power storage facility and connectRF network nodes 104 that require power to the power storage facility.

In an embodiment, the power required by an RF network node 104 may varyduring the duration of a reader 140 command and therefore the powershared by the RF network node 104 may change. For example, the requestfrom the reader 140 may request both a read and write of information tothe RFID tag 102. During the read operation, one of the RF network nodesmay require power and may receive power from the power storage facility.But during the write portion of the command, the same RF network node104 memory may be full and therefore the RF network node 104 may notparticipate in the write operation and may share power with the other RFnetwork nodes 104 by being isolated from the power storage facility. Itshould be understood that during a reader 140 command cycle, RF networknodes 104 may be switched on or off a plurality of times to share powerwith the RF network nodes 104 that require power.

In support of power harvesting, RF network node 104 power scheduling,and RF network node 104 power sharing, a method of power metering may beimplemented to accurately measure the amount of power being receivedfrom reader signal. Accurate and timely incoming power measurement maybe important to the operation of the RFID tag 102. For example, if thereader signal is in decline, the RFID tag 102 may not receive enoughpower to complete a write cycle. In this situation, the RFID tag 102 maydetermine to wait for the next reader cycle to start the write cycle ofthe reader 140 command. In another example, based on the amount of powermeasured by the power meter, the RFID network nodes may use powerscheduling, power sharing, or the like to extend the amount of time theavailable power can be used by the RFID tag 102.

In an embodiment, the power meter may provide power information to boththe reader 140 and the RFID tag 102. In the case of the reader 140, thepower meter may provide incoming power information back to the reader140. The reader 140 may use the power information to determine if thecurrent read cycle needs to be extended, to determine if another readcycle needs to be preformed, determine if the reader power needs to beincreased, or the like. In an embodiment, the reader may be able torecord a series of power meter power measurements to determine RFID tagpower profile rate of change. The power profile may be used to determineif the read cycle is continued, if the read cycle is repeated, if thereader 140 power is increased, or the like. The power profile may beused to predict how much power the RFID tag 102 may receive and may beused to make determinations of operations that can be completed with theremaining power.

In the case of the RFID tag, the power meter may provide power profilerate of change information, current power information, or the like tothe RFID tag 102. The power information provided by the power meter mayallow the RFID tag 102 to determine if an operation can be completed, ifan operation should be started, if an operation should be canceled, orthe like. In an embodiment, based on the power meter reading, the RFIDtag 102 may transmit information to the reader 140 requesting extensionof the current read cycle, requesting an additional read cycle,requesting increased reader 140 transmitted power, or the like. Thepower profile may be used to predict how much power the RFID tag 102 mayreceive and may be used to make determinations of operations that can becompleted with the actual or predicted remaining power. For example, thenext operation may be a data write and the RFID tag may determine if thewrite operation can be started with the predicted amount of power to bereceived. If the write operation cannot be completed with the predictedamount of power, the RFID tag 102 may request the reader to extend thecurrent read cycle, request an additional read cycle, request increasedreader 140 transmitted power, or the like.

In an embodiment, to provide accurate power readings from the reader 140signal, the RFID tag 102 power meter may include a flash analog todigital (AD) converter associated with the antenna 108. By placing theflash AD converter near the antenna 108, the incoming signal power maybe measured as the reader 140 signal is received by the RFID tag 102. Inan embodiment, an algorithm may be used to determine the amount of powerthat can be created by the RFID tag 102 from the received signal.

In embodiments, the data processing and controller 132 on the RFID tag102 may include digital circuitry that requires the clock 120oscillator. The systems and methods described herein may provide for theclock 120 circuit as part of the RF and analog block 302. The frequencyof the clock 120 may be a selectable value, such as 1 MHz, 3 MHz, 6 MHz,or the like. In embodiments the clock 120 oscillator may be specificfrequency and configuration, such as a 1.92 MHz starved ring oscillator,or other frequency and configuration that meets the needs of the RFnetwork node 104 and associated external interfaces. In embodiments, theclock 120 oscillator may require a specific oscillator frequency inorder to provide for accurate detection, reception, and transmission ofdata. In embodiments, the variation of the clock's 120 oscillatorfrequency may be highly accurate, such as +/−2.5% variation duringbackscatter. The presence of the highly accurate clock 120 oscillatormay better provide for reliable internal RF network node 104functionality and communications via interfaces external to the RFnetwork node 104. In embodiments, the clock 120 and data may not besynchronized between the RF network nodes 104 on the RFID tag 102.

In embodiments, the synchronization circuit 162 may calibrate maysynchronize the RF network nodes 104. Synchronization 162 may be relatedto synchronizing the phase of clock 120 oscillators on a plurality of RFnetwork nodes 104. For example, a synchronization signal may be sentfrom a master RF network node 104, the reader 140, another RFID tag 102,or the like, to synchronize all targeted RF network node 104 clock 120oscillators. Calibration may be related to the adjustment of the clock120 oscillator's frequency on the plurality of RF network nodes 104.Calibrating the clock 120 oscillator of each RF network node 104 to acommon clock 120 oscillator may be accomplished by transmitting acalibration signal among the plurality of RF network nodes 104. Thecalibration signal may be transmitted from each RF network node 104 ontothe inter-node communications interface 154 and simultaneously receivedby all RF network nodes 104.

In embodiments, the data processing and controller 132 may include aroutine for establishing which of the plurality of RF network nodes 104on the RFID tag 102 is to act as the master, this protocol is describedherein. The implementation of the protocol may require the use of arandom number provided to the routine running via the data processingand controller 132. In embodiments, a random number generator 122 maysupply the random number to the data processing and controller 132.

The random number generator 122 may be a computational or physicaldevice designed to generate a sequence of numbers or symbols that lackany pattern, i.e. appear random. Software-based routines for randomnumber generation 122 are widely used, but may fall short of this goal,though they may meet some statistical tests for randomness intended toensure that they do not have any easily discernible patterns. There aretwo principal methods used to generate random numbers. One may measure aphysical phenomenon that is expected to be random, and then compensatefor possible biases in the measurement process. The other may usecomputational algorithms that produce long sequences of apparentlyrandom results, which are in fact determined by a shorter initial seedor key. The latter type is often referred to as a pseudo-random numbergenerator.

The physical random number generator 122 may be based on an essentiallyrandom atomic or subatomic physical phenomenon, whose randomness may betraced to the laws of quantum mechanics. Examples of such phenomenainclude radioactive decay, thermal noise, shot noise, clock drift, andthe like. In an embodiment, clock drift may act as the random physicalsource from which the random number may be generated. Clock drift mayultimately be related to component differences, design differences,behavior changes caused by component aging, configuration and set updifferences, or the like. In embodiments, a plurality appropriatelyadjusted ring of oscillators may be employed that are summed byexclusive-or logic to generate the random number from the drift of theoscillators. Further, a logical enable signal may be provided toinitiate or terminate the action of the random number generator 122.Although clock drift represents an example of a configuration forgenerating the random number, it may be understood that anyconfiguration known to the art to generate the required random numbermay be employed.

In embodiments, the data processing and controller 132 may be a digitalportion of the RF network node 104 that functions as a central dataprocessing facility for command decoding, execution, and response; alogical control facility for state related functions; a memory storagefacility for the storage of short and long term data in volatile ornon-volatile memory; a program storage and execution facility forsoftware-based control of operational execution and market specificapplications; a data interface controller; and the like. In embodiments,the data processing and controller 132 may provide the function ofcentral processing unit for the RF network node 104, possessing programstorage, combinatorial and sequential logic, data bus interfaces, andthe like. In embodiments, the flexibility of the RF network node 104 toaccommodate a plurality of market functions may be partly associatedwith the data processing and controller 132.

In embodiments, the data processing and controller 132 receives andtransmits commands and data through a plurality of interfaces, includingthe demodulator 118, the modulator 128, the ESD and impedance matching110 block, a communications facility 134, and the like, as shown inFIG. 1. The data processing and controller 132 may be responsible forcommand decoding, encoding, encrypting, decrypting, execution, storing,and the like. A command may be an instruction, where an instruction is aform of communicated information that is both command and explanationfor how an action, behavior, method, or task may be begun, completed,conducted, or executed. In embodiments, the data processing andcontroller 132 may receive commands or instruction through thedemodulator 118 interface; decode the command; execute the command usinginternal storage, logic, external interfaces, or the like, to the dataprocessing and controller 132; gather requested data, action responses,sensor readings, communications, or the like, directed by the command;and transmit responses, telemetry, status, or the like, by way of themodulator 128 interface. In embodiments, command and response may alsobe via the direct RF network node 104 interface to other RF networknodes 104 on the RFID tag 102.

In an embodiment, an RFID tag 102 or RFID network node 104 may includethe method and system of interpreting commands from the RFID reader 140.In an embodiment, the amount of the RF network node 104 execution coderequired to execute the RFID reader 140 commands may be reduce by the RFnetwork node 104 generically processing commands sent by the RFID reader140 to the RFID tag 102. In an embodiment, the RFID reader 140 commandsmay contain a number of associated parameters for the execution of theRFID reader 140 command. An RF network node 104 generic processor may beused to divide the command into its individual parameters for processingby the RF network node 104. In an embodiment, the RF network node 104may recognize the RFID reader 140 command by the parameters associatedwith the command. For example, the RFID reader 140 may transmit acommand with the parameters operation code, memory bank, delay, and thelike. The RF network node 104 may recognize the RFID reader 140 commandas a memory read command by these associated parameters. The RF networknode 104 may execute the overall RFID reader 140 command by executingcode associated with the individual parameters. In an embodiment, themaster RF network node 104 may break the RFID reader 140 command codeinto parameters and execute the parameters or may request other RFnetwork nodes 104 on the RFID tag 102 to process all or some of theparameters. The master RF network node 104 may transmit information tothe RFID reader 140 based on the returns of the individually executedparameters. In an embodiment, the RF network node 104 may selectivelyexecute the RFID reader 140 command; based on the command's role in theRFID tag 102; the RFID tag 1102 may be able to execute any RFID reader140 command, but may not execute all of the RFID reader 140 commandsreceived. In an embodiment, by reducing the RFID reader 140 command codeinto generic parameters, the RFID network node 104 execution code may bereduced and may result in the RF network node 104 size beingsignificantly reduced. Additionally, there may be an increase in the RFnetwork node 104 functionality by executing RFID reader 140 commandsusing only the individual parameters to execute the entire RFID reader140 command.

In embodiments, the data processing and controller 132 on a RFID tag 102may support command encryption. Encryption may be a process of encodinginformation in such a way that only a processing device with theencryption key may decode it. The systems and methods described hereinmay utilize various systems of encryption, including symmetric-keyencryption, public-key encryption, digital certificates, and the like.In symmetric key encryption, each of the RFID tags 102 may have a keythat is used to encrypt or decrypt a packet of information. In symmetrickey encryption, each of the RFID tags 102 utilizing the encryptionscheme may require the key to communicate. In public-key encryption, acombination of a private key known only to the RFID tag 102, and apublic key given by the RFID tag 102 to any interface device attemptingcommunication, is used in the encryption design. Digital certificatesutilize a third independent source, often referred to as a certificateauthority, in the encryption design. In embodiments, any encryptionprocess known to the art may be used in implementing a securecommunications design. The implementation of an encryption scheme withinthe communications design of an embodiment of the invention may providegreater reliability of operation, as well as secure processing of themarket implementation. In embodiments, encryption may be utilized in anycommunications external to the RFID tag 102, such as the RFID tag 102 tothe reader 140, the RFID tag 102 to the RFID tag 102, the RFID tag 102to external facilities 138, and the like.

In embodiments, the data processing and controller 132 may supportproprietary command protocols that may be specific to the systems andmethods described herein, specific to a market 150 application, specificto a geographic location, or the like. The data processing andcontroller 132 may also support the international standard EPCglobal UHFclass 1 generation 2 (Gen2) for the use of RFID tags. The Gen2 standardspecifies protocols for the RFID tag 102 air interfaces, the protocolfor exchanging information between the RFID tag 102 and the reader 140.

Referring to FIG. 1A, in embodiments the communications facility 134 maybe a communications facility 134B that is part of the data processingand controller 132 on the RF network node 104, a communications facility134A on the RFID tag 102 in communication with the data processing andcontroller 132, or both. The communications facility 134 may interfacewith a plurality of external facilities 138, such as sensors 138A,displays 138B, a gateway 138C, a peripheral 138D, a network 138E, adevice 138F, an actuator 138G, and the like. The communications facility134 may utilize a serial interface to communicate with externalfacilities 138, such as an I²C bus, an SMBus, a PMBus, an SPI bus, a1-wire bus, and the like. For instance, an I²C bus (Inter-IntegratedCircuit bus) is a multi-master serial computer bus that may be used tocommunicate between the data processing and controller 132 and low speedexternal facilities 138. The SMBus (System Management Bus) represents asubset of PC that defines stricter electrical and protocol conventions,where many PC systems incorporate policies and rules from SMBus. ThePMBus (Power Management Bus) is a further variant of the SMBus which istargeted at digital management of power supplies Like SMBus, it is arelatively slow speed two wire communications protocol based on I²C.Unlike either of those standards, it defines a substantial number ofdomain-specific commands rather than just saying how to communicateusing commands defined by the reader. The 1-Wire bus is similar inconcept to I²C, but with lower data rates and longer range. The SPI Bus(Serial Peripheral Interface bus) is a synchronous serial data linkstandard that operates in full duplex mode, and is sometimes referred toas a “four wire” serial bus, contrasting with three, two, and one wireserial buses. One skilled in the art will appreciate that there are alarge variety of serial buses that may be used by the invention incommunicating with external facilities 138, including non-standardinterfaces, and so the list and description provided herein should notbe taken as limiting in any way.

In embodiments, the RFID tag 102 may act as the master on thecommunications bus, where the external facility 138 would act as theslave. Alternately, the external facility 138 may act as the master andthe RFID tag 102 the slave. For instance, the RFID tag 102 may act as aslave to a sensor 138A and automatically store historical records ofsensor activity. In embodiments, one way to implement this could be tohave the RFID tag be considered a serial bus slave, such as an I²C busslave, and an external sensor act as the bus master. The externalsensor, being the master, may then initiate data transfers, and sensorinformation that ends up as raw data in the RFID tag slave device. Inembodiments, another way to implement this could be to have the RFID tag102 automatically store the sensor data as a history record in a memorystructure similar to an ATA container. In embodiments, the RFID tag 102may not be using the raw address received from the serial bus to writeto that location in memory but instead may be keeping track ofpreviously written records and putting new data in the proper location.Later on, when an interrogator comes along, it may use the table ofcontents in memory to know if any of the history records are ofinterest. This design could also be flexible enough to format the memorybased on data contents. For example, the bus master might send anaddress along with 16 bytes of data. The data may have actually comefrom a plurality of different sensors and could be split into differentrecords, or into a single record with identifiers for each piece ofdata. In embodiments, compression schemes may also be utilized, such asstandard schemes or application specific schemes, to compress the sensordata before storing it in memory.

In embodiments, the communication facility 134 interface to externalfacilities 138 may support the implementation of a broad range ofapplications, such as sensor tags, display tags, smartcards, medicaluses, and the like. For instance a sensor tag may store temperature,stress, or any other information accumulated by a sensor. For instance,sensors linked to RFID tags may have many military applications, rangingfrom recording storage conditions of materials, calibrations forequipment, storage of usage information of equipment, and the like. Forexample, it may be necessary to keep track of how many times a tank hasfired a round through its barrel, and that after a set number of firingsthe barrel may have to be replaced. In this instance, the presentinvention may combine with a sensor on a tank gun barrel to count howmany times its fired, such as through sensing the temperature, where thesensor downloads the information to the tag 102 via the communicationsfacility 134, as described herein. In another instance thecommunications facility 134 may allow the present invention to beintegrated into smart-commerce applications, such as smart cards. Forexample, smartcards may utilize the present invention in the smart cardto automate or make it easier to write information to a smart card, e.g.Bank card. The serial bus associated with the communication may then beburned so that that information could not be changed. In anotherinstance the communications facility 134 may allow the present inventionto be used in medical applications, such as using the tag 102 incombination with a medical testing system that would download the testresults into the tag for later reading.

In embodiments, the present invention may be used in conjunction with adisplay 138B, such as an ‘electronic paper’ display, e-ink display,liquid crystal display (LCD), thin-film transistor display (TFT),organic light-emitting diode display (OLED), nano-crystal displays, andthe like. In embodiments, a display 138B may be a stand-alone outputdisplay or a display module, where the display module may include otherfunctions, such as display driver electronics, control functions, andthe like, in addition to the output display. In embodiments, the presentinvention may be able to store and send information to a display 138Bthat is powered by an external source (i.e. not powered through the tag102), supplied power from the tag 102 to change the displayedinformation and where the display 138B requires no power to hold displayinformation, and the like. For example, electronic paper, also callede-paper, is a display technology designed to mimic the appearance ofordinary ink on paper. Unlike a conventional flat panel display, whichuses a backlight to illuminate its pixels, electronic paper reflectslight like ordinary paper and is capable of holding text and imagesindefinitely without drawing electricity, while allowing the image to bechanged later. To build e-paper, several different technologies exist,some using plastic substrate and electronics so that the display isflexible. E-paper may be considered more comfortable to read thanconventional displays. This may be due to the stable image, which doesnot need to be refreshed constantly, the wider viewing angle, and thefact that it uses reflected ambient light. One example of e-papertechnology is e-ink, a technology that requires ultra-low powerconsumption. The principal components of electronic ink are millions oftiny microcapsules, about the diameter of a human hair. In oneincarnation, each microcapsule contains positively charged whiteparticles and negatively charged black particles suspended in a clearfluid. When a negative electric field is applied, the white particlesmove to the top of the microcapsule to become visible to the reader.This makes the surface appear white at that location. At the same time,an opposite electric field pulls the black particles to the bottom ofthe microcapsules where they are hidden. By reversing this process, theblack particles appear at the top of the capsule, which now makes thesurface appear dark at that location. To form an E Ink electronicdisplay, the ink is printed onto a sheet of plastic film that islaminated to a layer of circuitry. The circuitry forms a pattern ofpixels that can then be controlled by a display driver. Thesemicrocapsules are suspended in a liquid “carrier medium” allowing themto be printed using existing screen printing processes onto virtuallyany surface, including glass, plastic, fabric and even paper. Inembodiments, the present invention may be used in conjunction with anelectronic paper display, where the tag 102 may provide power to thedisplay 138B when information is updated, but where the display 138Bdoes not require power to maintain the displayed output. One skilled inthe art can appreciate that the combination of the present invention andelectronic paper technology may enable a variety of applications, suchas human readable labels (i.e. without the aid of an RFID reader) wherethe tag 102 holds information to be displayed and where the tag 102 mayhave that information updated resulting in a change to the displayedinformation. In embodiments, the updating of the information may comefrom an update provided through an RFID reader, a second tag 102, anexternal facility 138, and the like. In embodiments, the presentinvention's memory capabilities, as described herein, may provide agreater amount of data storage to be made available to the displayapplication than would be otherwise available.

In embodiments, the present invention used in conjunction with a display138B, such as with an electronic paper display, may be used to replacetags such as paper tags, metal plate tags, and the like. For instance,electronics equipment may need to be tagged to carry information such aspart and manufacturing data, modifications, updates, part number,inspection data, calibration data, safety data, and the like. Inembodiments, applications of the present invention to providing humanreadable tag 102 labels may include tags for avionics equipment, wherethe amount of information to store on the label may require the largememory capabilities of the present invention as described herein. Forexample, companies like Boeing and Airbus may benefit from a high memoryRFID to keep track of maintenance events, equipment configuration, andthe like. The present invention may provide a solution where previouslyrelatively static plates or labels are replaced by a reprogrammabledisplay 138B attached to the asset for purposes including the trackingof identification, configuration, maintenance, calibration and otherinformation. In embodiments, the present invention may use a changeabledisplay 138B in lieu of metal plate tags, paper label, and the like,where the display 138B may be changed by electronic means by directcontact, magnetic fields, electromagnetic waves, and the like, toprovide new information. The display 138B may be used in combinationwith RFID label data such as an electronic product code or uniqueidentifier. The display 138B may be used in combination with a highmemory RFID tag 102 that records pertinent changes to the tagged item.The display 138B may use power to change the display 138B as provided byan RFID reader, by an integrated battery, by an energy storage device,by fuel cells, by capacitors, as harvested from external power sources(e.g. via temperature gradients, light receptors, etc), by directelectrical connection from another device, and the like. In embodiments,the display 138B may have the dimensions, materials, and configurationthat are configured to allow for efficient performance of an RFIDantenna within the device. The thickness of the tag display 138B may beincreased beyond typical practice in order to allow for operation whenmounted on metal. A dielectric material may be used so as to providetuning for the antenna or to reduce the thickness of the device. Inembodiments, the antenna may be based on a dipole, a slot antenna, amonopole, and the like. The antenna may be configured for operationcapacitively or inductively using near-field physics. The display 138Bmay include a bar-code including 1D and 2D barcodes. The display 138Bmay include changeable configuration information. In embodiments,programmability or re-programmability of the tag 102 associated with thedisplay 138B may derivative from fixed or hand-held solutions. Thedisplay 138B may be synchronized with a database in some manner. Thedisplay 138B may be in combination with a contact memory button, withreal time location functionality, and the like. The display 138B may beused in reusable applications such as transportation totes, taggedpallets, and the like. The display 138B may have an interface betweenRFID tag 102 and display 138B that is serial in nature, as describedherein, to minimize pin-outs.

In embodiments the present invention may provide power 170 to or fromexternal facilities 138, as well as from other outside sources 172 (e.g.battery power) to enable a flexible power scheme to a wide range of RFIDapplications. For example, the RFID tag 102 could provide power 170 toan external facility 138 to provide a fully passive battery freeoperation, have power supplied from the external facility 138 to providehigher power applications, have power supplied from an external sourcethrough the external power interface 172 to provide an active orsemi-active solution, and the like. In embodiments, the presentinvention may provide power to an external facility 138 even when theonly source of power is the RFID reader 140. That is, an externalfacility 138 may be powered when the RFID tag 102 is operating as apassive tag.

In embodiments, the data processing and controller 132 may providememory for the storage of commands, command tables, the RFID tag 102health and status information, data, program storage, registerinformation, encryption keys, control states, and other uses of digitalmemory known to the art. The data processing and controller 132 mayutilize a plurality of memory 162 technologies, including random accessmemory (RAM), static RAM, dynamic RAM, read only memory (ROM), programread only memory (PROM) electrically erasable (EEPROM), flash memory,and the like, including other volatile or non-volatile memorytechnologies known to the art. In embodiments, the data processing andcontroller 132 may manage the memory 162 with a memory manager 164,where the memory manager 164 may manage not only memory 162 on its ownRF network node 104, but on other RF network nodes 104, such as when itsown RF network node 104 is a master RF network node 104

In embodiments, memory located within the data processing and controller132 may be partitioned, segmented, blocked, and the like, into aplurality of functional areas, including areas that are public, private,encoded, volatile, non-volatile, shared, distributed, and the like. Anexample of a public area of memory may be a portion of memory that isreadable by unsecured facilities, such as public readers; portablepublic readers; other RFID tags 102 with public storage; and the like.An example of a private area of memory may be a portion of memory thatis only readable by secured facilities, such as market specific readers140, application specific readers 140, company private facilities, andthe like. Private areas of memory may also be encoded to increasesecurity or the level of privacy afforded by a secure portion of memory.

In embodiments, memory located on the RF network nodes 104 on the RFIDtag 102 may be shared, distributed, common, or the like. An example of ashared memory may be memory on the RF network nodes 104 that may beshared by the other RF network nodes 104, accessed by the other RFnetwork node 104 data processing and controllers 132, made available tothe other RF network nodes 104, or the like. An example of distributedmemory may be memory utilized by one RF network node's 104 dataprocessing and controllers 132 across one or more other RF network nodes104 resident on the same RFID tag 102. An example of common memory maybe memory areas on the RF network nodes 104 that are made available tothe other RF network nodes 104, such that the memory is available forcommon use by all of the RF network nodes 104. Because of the inter-nodeinterface 154 made available through the RFID tags' 102 common antennaconnection 158, memory across the RFID tag 102 may be utilized in aplurality of ways amongst the RF network nodes 104 on the RFID tag 102.The ability of these systems and methods to communicate directly fromthe RF network node 104 to the RF network node 104 may enable aplurality of memory use configurations. These various memoryconfigurations may provide significantly greater memory storage, whichmay in turn allow for greater functionality and the market 150capability.

In embodiments, the data processing and controller 132 may function as amemory manager, such as for the management of memory that is shared,distributed, common, or the like. An example of memory managing sharedmemory may be having the master RF network node 104 acting as the memorymanager. In this instance, the master RF network node 104 may set uppartitions or boundaries in the extended memory space available acrossthe plurality of the RF network nodes 104 resident on the RFID tag 102.The master RF network node 104 may also allocate which of the RF networknodes 104 have access to certain areas of shared memory, arbitratebetween the RF network nodes 104 when there is contention for the samememory space, alter memory allocations and resources as processingrequirements change, and the like. Similar memory management activitiesmay be utilized for distributed or common memory, where the master RFnetwork node 104 may control memory allocations and access.

In embodiments, areas of memory may require authentication verificationto gain access, where different areas of memories require uniqueauthentications. For example, there may be three areas of memory, onepublic, one private, and one private-encrypted. The public area ofmemory may not require any authentication to gain access. The privatearea of memory may require some form of authentication, perhaps apassword or the like. The private-encrypted area of memory may requiresome form of authentication, as well as some form of encryption key togain access. In embodiments, the ability to block off segments of memoryinto a plurality of sizes, uses, markets 150, access, encryption, andthe like, in combination with the ability share memory across the RFnetwork node 104 boundaries may better enable the RFID tag 102 to beused in a variety of markets 150.

In embodiments, memory may be utilized to process data intelligently.For instance, rather than being limited to storing and transmitting rawdata to the reader 140 or the other RFID tags 102, the RF network node104 may perform processing steps on the raw data, and store thispost-processed data in memory for subsequent transmission. An example ofthis may be the conversion of raw sensor 138A data, such as a voltagelevel, and performing post-processing to convert this raw voltage levelinto a temperature value. Calibration tables may also be resident inmemory, and available for use in the conversion to temperature value,based upon the characteristics of the sensors 138 interfaced to theparticular RF network node 104. In embodiments, conversion orcalibration values may be transmitted to the RFID tag 102 memory, orstored in the RFID tag 102 at the time of manufacture. There may bedifferent conversion and calibration values for each of the sensors 138,and so a data table may exist in memory for this purpose. The ability ofthe RFID tag 102 to perform intelligent data processing may decrease theprocessing requirements of the reader 140 or other communicating RFIDtags 102, which may enable the use of simpler reader 140 facilities,such as portable readers 140, or enabling reduced post-processing, suchas simpler RFID tag 102 to RFID tag 102 data processing, or the like.

Referring to FIG. 1A, a depiction of a block diagram embodiment withmajor components of an RFID tag is shown. In an embodiment, the dataprocessing and controller 132 may be responsible for processing theinformation received from the RF and analog block 302. The processingmay include analytical work on the data such as calculations,conversions, encryption, decryption, searching, storing information tomemory 162, receiving information from memory 162, or the like. Thememory 162 may be a continuous memory, partitioned memory, or the likewhere the information received from the RF and analog block 302 and thedata processing and controller 132 may be stored. In an embodiment, thememory 162 may be one time programmable memory (OTP), many timeprogrammable memory (MTP), a combination of OTP and MTP memory, or thelike.

In an embodiment, information stored on the RFID tag 102 may besearched. The search may be at the request of the reader 140, as part ofa process on the RFID tag 102, or the like. Because of the limitedamount of power with which an RFID tag 102 has to perform a requestedtask, RFID tag searching may be designed to consume the least amount ofpower. The RFID tag 102 search may include a look-up table, contentaddressable memory (CAM), brute force search of all memory locations,bit matching, or the like.

In the example of a content table, there may be a look-up table that maystore the location of certain information. The location informationstored in the content table may be a pointer to certain memorylocations, a pointer to memory regions, a pointer to fixed allocatedmemory words, a pointer to dynamic allocated words, or the like. Forexample, the content table may store information on an objects currentname and price information is stored. When a request is received for theobjects price, the search sequence may be to look up the informationlocation in the content table and the content table my point directly tothe price memory location. The content table may be search using wordmatching, brute force, binary matching, or the like. It should beunderstood that the content table may use many different methods to findmemory information and this example is not to be considered the onlymethod of finding information using a content table.

An RFID tag 102 search may also be performed with CAM where the entirememory content is searched for the desired information. Using CAM,information within memory may be indexed by content and using CAM theindex may be searched to retrieve a memory pointer that points to theinformation within the memory. For example a phone book may be set up incontent addressable memory where a name look up is performed. The namemay be found in the indexed content where a pointer may point to thememory location of the name and the same memory location may includeadditional information related to the name such as a phone number,address information, or the like.

In an embodiment, a binary CAM may be used in a tag memory search. Inbinary CAM, all the memory is matched to a binary search term using thebinary numbers 1 and 0. The binary CAM may include a comparator tocompare the search word to the word found in memory. The binary CAMsearch may return a first match, all matches, or the like.

In an embodiment, a ternary CAM may also be used. The ternary CAM mayadd a third character called “don't cares” where the binary search termmay be masked with a character for binary numbers that are not importantto the search. For example, the search may be on the word “10XX11”,where the “X” is the masking character, and the ternary CAM search mayreturn matching words “100011”, 100111″, “101011”, and “101111”. Thebinary CAM and ternary CAM searches may be considered a parallelsimultaneous search of all memory locations. The binary and ternary CAMmay require low levels of power because instead of reading memorylocations, a hardware parallel lookup that can be performed quickly andwith less power.

In an embodiment, in addition to content look-up tables and CAMsearches, there may be specialized application specific dataorganization that may allow very quick data searches on an RFID tag 102.In one embodiment, an application specific data organization may locateinformation in specific memory locations for rapid retrieval ofinformation. Data organizations that look to specific memory locationsmay be considered non-search searches because a full memory search isnot required to find the information required. In an embodiment, theremay be a number of different methods the a non-search may be executedsuch as a content table storing the location of specific information,information stored in specific memory locations, memory informationindexed in a certain order, and the like.

In an embodiment, another method of finding information on an RFID tag102 may be using a table of contents within the memory. The table ofcontents may divide the RFID tag 102 memory into regions of memory thatcontain certain types of memory, then a pointer or series of pointersmay point to these memory regions. In an embodiment, the table ofcontents may be combined with other searching methods to findinformation. For example, a search may use the table of contents tonarrow a search to a particular region of memory and then use a binaryCAM search to locate the particular information. An example ofinformation searching may be in the aviation industry. An RFID tag 102may be associated with an aircraft component and may record and storethe archival history of the component. The component RFID tag 102 maystore information related to manufacturing, flight cycles, maintenance,and the like. In searching for information, the table of contents may beused to find the memory region containing the desired information, suchas maintenance history, and then may user a binary CAM search to locatethe specific information required. In an embodiment, the table ofcontents may be organized for each type of application for which theRFID may be used.

In an embodiment, the memory 162 may include OTP memory. For use onmultiple RF network node 104 RFID tags 102, the OTP memory may providebenefits such as high memory density, fast access times, fieldprogrammability, low programming voltage, short programming times, MTPemulation (eMTP), the ability to mask ROM, scalability, wide I/O buscapability, redundancy, security, energy efficiency, or the like. Themultiple RF network node 104 may be able to coordinate the OTP memoryassociated with multiple RF network nodes 104 using the communicationbus among the RF network nodes 104. In an embodiment, the OTP memory maybe implemented differently depending on the use of the RFID tag 102. Forexample, the OTP may be divided into at least one memory word or may bedivided into segments that may include more than one memory word, butmay represent one memory address. The organization of the words andsegments may provide for one time writing of information to the wordmemory or information may be written more than once to segments that maycontain multiple word storage. The multiple word storage for the segmentmemory may be considered the depth of writing. In other words, thesegment may provide for information to be written to the same storageword address for the number (depth) of words associated with thesegment. Segment depth will be described in more detail below. In themultiple RF network node 104 RFID tag 102, the OTP memory may be on someof the RF network nodes 104 or all the RF network nodes 104. Each RFnetwork node 104 may provide control of the OTP memory that may be onthe RF network node 104. Additionally, all of the OTP memory of theindividual RF network nodes 104 may be coordinated by a master RFnetwork node, or in a distributed manner without a master node.Furthermore, the OTP memory may be coordinated as a single memory store,coordinated as redundant memory stores, coordinated as separate memorystores, or the like depending on the requirements of the RFID tag 102.

In an embodiment, the OTP memory may be a write once memory whereinformation may be written to the OTP memory only once, but may be readmany times. Information may be written to the OTP memory while on thewafer, prior to when the RFID tag 102 is associated to an object, afterthe RFID tag 102 is associated to an object, or the like. For example,information may be written to the OTP memory at a manufacturer before oras the RFID tag 102 is associated with an object to provide informationon the object such as a part number, a serial number, pricinginformation, manufacturing information, quality information, or thelike. In another example, an enterprise may purchase RFID tags 102without stored information and may apply information to the RFID tag 102after the RFID tag 102 has been associated with an object at theenterprise such as object location, object price information, storageinformation, date information, delivery information, or the like.

In an embodiment, the OTP memory may be implemented as a single memorystore, as a redundant memory store, as a combination of single andredundant memory stores, separate memory stores, or the like. The OTPmemory may be divided into smaller memory stores to be used as redundantmemory where the RF network node 104 may store the same information inmore than one of the smaller memory stores. For example, an 8K OTPmemory may be divided into two redundant 4K OTP memory stores, and wheninformation is stored to the OTP memory, the same information may bestored to both of the 4K memory stores. This may provide a redundantmemory system that may allow retrieval of the stored information even ifthere is a failure of one of the memory stores. It may be understood byone skilled in the art that the OTP memory may be configured in a numberof different ways consistent with the present invention.

In an embodiment, the OTP memory may be configured as a write oncememory where the manufacturer, enterprise, or other user of the RFID tag102 may store information to the available OTP storage space. In thisembodiment, the OTP memory may only be able to receive information once;the information may be written to the OTP memory starting at thebeginning of the storage location and may be sequentially written to theend of the information to be stored. This method of OTP memory may beuseful for storing information such as a part number, serial number,pricing information, and the like.

In an embodiment, different locations of the OTP memory may be assignedto different information. For example, part number information may beassigned memory locations 1-7 and serial number information may beassigned memory locations 8-14. In an embodiment, there may be an end offile indicator, end of record indicator, record pointer, or the like todefine the end of a certain memory location. For example, at the end ofstorage location 7, there may be an end of record pointer to indicatethat this is the end of the part number information. Using this storagemethod, the part number may be stored at one time and the serial numbermay be stored at another time on the same OTP memory. In an embodiment,the data processing and controller 132 may be programmed as to whichinformation is to be stored in certain locations of the OTP memory andas to the management of storing the proper information to the assignedmemory locations.

In an embodiment, using this method, the data processing and controller132 may store the different available memory locations in aconfiguration table to define where information is to be stored. In anembodiment, the RFID tags 102 may be industry-specific, where the dataprocessing and controller 132 may be programmed to assign information tocertain OTP memory locations. For example, a retail store RFID tag 102may store part number, serial number, and pricing information todifferent locations on the OTP memory, with the pricing informationbeing written once the object and RFID tag 102 are received in theretail store. In another example, the aviation industry may store partnumber, serial number, and FAA required information to the OTP memory;for example, the FAA information may be written to the RFID tag 102 overthe life cycle of the aviation component to a different set of locationswithin the OTP memory. It may be understood by one skilled in the artthat there may be many different types of information stored to OTPmemory using this information writing protocol.

In another embodiment, the OTP memory may emulate MTP (eMTP) memory byproviding a protocol to write information to the same RFID tag 102memory location more than once. In MTP memory, information may bewritten to the same memory location more than once, but OTP may only becapable of writing information in a certain memory location once. Toemulate MTP memory, the OTP memory may have more than one memory wordrelated to the storage address for the same information. In anembodiment, the information may be stored in a section of memory calleda segment and the segment may have a plurality of memory wordsassociated to it for storing written information more than once. In thismanner, the information may be considered being written to a virtualmemory location. The information may be virtually written to the segmentwhile the information is actually written to the physical location ofone of the memory words in the segment. For example, in storing anobject's price to eMTP memory, the segment storing the price may have anumber of memory words in which to write the price. The first time theprice is written to the segment, the price may be written to the firstword associated to the segment. With the writing of the priceinformation to the first segment word, it may be recorded within thesegment that the first segment word contains the pricing information. Adifferent price may be written to the same segment a second time, thissecond price may be written to the second word in the segment, and itmay be recorded with the segment that the second word contains the lastwritten pricing information. Therefore, when there is a read request forthe pricing information, the pricing segment may be read to determinethat the second word has the latest price. It should be understood thatthe segment may have a plurality of memory words associated to it andinformation may be written to the segment for as many times as there arewords associated with the segment. For example, if the segment has fourassociated words, then information may be written to the segment fourtimes before the segment is considered full and cannot be written toagain. However, there may be additional segments that may be dynamicallyallocated should the pricing information change again. Dynamicallyallocated segments may be allocated on demand, when the previous segmenthas been completely written to and the pricing information changes onceagain. Dynamic allocation of memory will be further described below.

In another embodiment, MTP memory may also be used to store all the RFIDtag 102 data. The data stored within the MTP memory may be informationthat may be written more than once. For example, a retail store maychange the price of an item many times over the time the item is on ashelf; this information may be written to MTP memory. In this case, thechanges in price may be written either to the same MTP memory locationevery time the price is updated on the RFID tag 102 or to a differentMTP memory location.

In another embodiment, the data processing and controller 132 mayincorporate both OTP and MTP memory for saving information to the RFIDtag 102. Among other things, the MTP memory may be used to store addressinformation about the OTP segments within a table; the addressinformation may be stored in variables within the MTP table. The MTPtable variables may be written an unlimited number of times to track theaddress information of the OTP segments. As new information is writtento the next OTP word memory, the MTP table may be updated with thememory word address information. Using MTP memory to store the OTPsegment memory address information may allow the use of a small amountof MTP memory to track large amounts of OTP memory segments by storingsegment information within the MTP table using multiple writes to thesame table variable. For example, in the aviation industry, as new FAAinformation is received by the RFID tag 102, the data processing andcontroller 132 may determine the next OTP segment to store theinformation, store the segment address information into the MTP tablevariable, and then store the new information in the correct storagelocation within the OTP memory.

Information within the OTP memory may be burned in and may not requirean electrical charge to maintain the stored information. This may allowthe multiple RF network node 104 RFID tag 102 to manage the power on theRFID tag 102 using the power management 130. The power to the OTP memorymay be managed based on the type of command received by the RFID tag102, based on where the information is stored, or the like. For example,if the RFID tag 102 command does not require a memory recall or memorystorage, the power management 130 may not power the OTP memory. Inanother example, depending on where information is stored within the OTPmemory, the power management 130 may only power a portion of the OTPmemory. Additionally, since the OTP memory is burned in, power may notbe required to maintain the information stored within the OTP memory andtherefore may not require initial powering to store information,periodic powering to maintain the stored memory, or the like.

Referring to FIG. 1B, an embodiment of storing information within OTPmemory using a segment table 202 and data maps (204 and 208) is shown.In an embodiment, the segment table 202 may store pointers (addresses)for data stored in the data maps (204 and 208). The segment table may beimplemented as OTP memory, MTP memory, a combination of OTP memory andMTP memory, eMTP memory, or the like. As OTP memory, there may be a setnumber of available pointers to point to the next memory writingposition, point to existing information in a memory position, or thelike. In an embodiment, the segment table 202 may be divided into anumber of segments to store pointer information and the segments may begrouped into sets of segments for pointing to information within thedata maps (204 and 208); the number of segments within a segment groupmay be dependent on the organization of the data maps (204 and 208). Asnew information is written to a data map (204 and 208) the next segmentwithin a segment group may be written with a pointer to the newinformation.

In an embodiment, the data maps (204 and 208) may be organized as directmaps 204 and segment maps 208. In an embodiment, direct maps 204 may bedata locations that may be intended to contain certain information. Inan embodiment, the direct maps 204 may be used by the owner of the RFIDtag 102 to write owner information to particular memory locations withinthe direct map 204; the direct map 204 may be divided into dataaddresses that may be used to store the certain types of data the ownermay save to the RFID tag 102. For example, the owner of the tag may bean aviation enterprise that may write maintenance information to theRFID tag 102 and may require a certain number of data addresses to storethis information. For this example, there may be direct map 204 dataaddresses for each of the saved maintenance records. In an embodiment,each data address within the direct maps 204 may be used to storecertain types of data. In embodiments, data may span more than one dataaddress, data may be a portion of a data address, or the like.

In another embodiment, the data addresses of the direct map 204 may beused to emulate MTP (eMTP) memory by allowing information to be writtento each direct map address more than once. In this case, each dataaddress may have a plurality of associated memory words to storeinformation in OTP memory. As shown in FIG. 1B, there are four memorywords for each of the eight direct map 204 data addresses. The number ofmemory words that are associated to a direct map address may beconsidered the direct map write depth. For example, in the direct map204 of FIG. 1B, the write depth is four. With a write depth of four,information may be written to each direct map memory address four timesbefore the memory address is considered full. For example, the firsttime information is written to a certain memory address, the informationmay be written to memory word one. If new information is required to bewritten to the same direct map 204 memory address, the next informationmay be written to memory word two. Writing to the next write locationfor a particular memory address may continue until the last memory writeword is filled with information. In FIG. 1B direct map 204, four datawords are shown for each user address, it should be understood bysomeone knowledgeable in the art that there may be any number of useraddresses and data words for information storage. Additionally, itshould be understood that there may be a variable number of data wordsfor the addresses within a direct map 204 where some addresses havedifferent write depths from other addresses. For example, addresses 1-10may have a write depth of four and addresses 11-20 may have a writedepth of six. In an embodiment, there may be an algorithm to determinewhat is the next available direct map 204 word to which information isto be written and the most recent written direct map 204 word from whichto read the information.

In an embodiment, the segment maps 208 may be used for storage of anyinformation that may be written to the RFID tag 102. Similar to thedirect map 204, the segment maps 208 may contain an individual elementof data, data may span more than one data block, data may be a portionof a data block, data may be stored using the set write depth of thememory address, data may be stored using a variable write depth, or thelike. In FIG. 1B segment map 208, six data words are shown for eachaddress, it should be understood by someone knowledgeable in the artthat there may be any number of addresses and data words for informationstorage.

In an embodiment, the segment map 208 may use a fixed write depth, avariable write depth, a combination of fixed and variable write depths,or the like. In an embodiment, a fixed write depth may include eachsegment in the segment table 202 associated to a fixed number of memorywords to store information. As shown in FIG. 1B, the segment table 202has a fixed write depth of six memory words. As information is writtento the segment, the next OTP memory word is used to store the newinformation. Once the segment has been written to for the six memorywords, that memory segment may be considered full. It should beunderstood that while one segment may be considered full, other segmentswithin the segment table may have memory words that have not yet beenwritten and therefore are not considered full.

In another embodiment, the segment map 208 OTP memory may use a variablewrite depth. In an embodiment, as a segment is considered full becauseall of the segment words have been written, memory words from othersegments that have not been written may be associated to the fullsegment address. For example, if the six memory words associated with afirst segment are all written, a second segment, and associated memorywords, may be used to continue storing information to the first segment.In the segment map configuration shown in FIG. 1B, this may then providethe first segment with twelve memory words to store information. As moreinformation is stored to the first segment, additional other segmentscontaining unused memory words may be associated to the first segment tocontinue storing information to the first segment and thereforeincreasing the write depth of the first segment. In an embodiment, amemory protocol may be used for the variable write depth to associatethe first segment with additional segments. In an embodiment, the firstsegment may use all of the second segment words, may use some of thesecond segment words, or the like. In an embodiment, if some of thesecond segment words are used by the first segment, the write depth ofthe second memory may be reduced to account for the information writtenfrom the first segment and the write depth for the first segment may beincreased.

In an embodiment, instead of predefined fixed segments and fixed memoryword locations, the OTP memory may dynamically allocate segments,dynamically allocate memory word allocations, dynamically allocatesegments and memory word allocations, or the like.

In an embodiment, dynamically allocating memory words to segments mayinclude predefined segments within the segment table 202 that do nothave associated memory words. In an embodiment, there may be a pluralityof memory words defined within an OTP memory space that may bedynamically allocated to a segment as the segment requires additionalmemory words. The number of memory words may be related to the amount ofmemory available and the size of the memory words. In an embodiment, asinformation is stored to the segment, the segment may be allocated amemory word from the plurality of defined memory words. In anembodiment, a plurality of memory words may be allocated to a segment.In an embodiment, the segments within the segment table 202 may havedifferent numbers of memory words allocated. For example, using thedynamically allocated memory words, a first segment may have ten memorywords allocated and a second segment may have two memory wordsallocated. The dynamic allocation of memory words may continue until allof the predefined memory words have been allocated to segments.

In an embodiment, dynamically allocating segments may include adding thesegment to the segment table 202 as previously undefined information isadded to the OTP memory. In an embodiment, initially, the segment table202 may be without defined segments. As new information write requestsare made to the OTP memory, the new segment may be created and added tothe segment table 202. As the new segment is added to the segment table202, memory words may be allocated to the segment as a fixed memory wordallocation or the memory words may be dynamically allocated as describedabove.

In an embodiment, the dynamic allocation of segments and word memory maybe implemented as a combination of MTP and OTP memory or may beimplemented as only OTP memory. An example of using a combination of MTPand OTP memory may be to implement the segment address table 202 as MTPmemory and the memory words using OTP memory. This configuration mayallow the unlimited rewriting of segment address information to the MTPmemory to track the OTP word that is storing the latest information inthe OTP word memory.

In an embodiment, all of the RFID tag 102 memory may be implementedusing only OTP memory. Both the segment table 202 and the word memorymay be implemented using only OTP memory. As previously described, OTPmemory may be used to store information into word memory that isallocated to a segment within the segment table 202. In thisconfiguration, the segment table 202 may also be implemented using OTPmemory, the segment table 202 allocation may be fixed or dynamic. Inusing OTP for the segment table 202, the next segment may be determinedby using a bit map, deducing the next address by counting the number ofsegments already allocated, or some other address tracking method. Inthe case of the bit map, setting a bit to 0 or 1 for each segmentaddress allocated may map the allocated segment and may be used todetermine the next segment. In the case of deducing the segment, thenumber of segments already written may be counted during the writeoperation to determine the next address for a segment. In an embodiment,the choice of which method to use to determine the next segment may bethe method requiring the least number of reads to determine the nextsegment.

An example of using a bit map for determining the next segment mayinclude determining the number of the segments to allocate by countingthe bits in the segment table 202, storing the segment number in thesegment table 202, writing the bit in the segment bitmap thatcorresponds to the segment, writing the data and bit into the newsegment, and the like.

In an embodiment, when storing information to the segment and/or theword memory, special considerations may be used to account for theavailable power to store the information. In an embodiment, if the powerlevel is above a certain power threshold, the writing operation mayproceed, but if the power level is below the power threshold, thewriting operation may not proceed. In an embodiment, there may bespecific algorithms for writing information to the RFID tag 102 to allowfor recovery from the power level transitioning to a level below thethreshold during a write operation to properly write all the informationor to allow a recovery point from the interrupted write operation. In anembodiment, a verification bit may be written as part of the informationwrite process to provide an indication if the write process completedand the stored information is correct. In an embodiment, theverification bit may be written after the information is written, theverification bit may be written before the information is written, orthe like.

In an embodiment, the flow chart on FIG. 1C shows a careful writealgorithm that may allow for recovery from a low or no power situationduring a write operation. The first step 210 may be to start with avirtual address and data to write. The next step 212 may be to determinethe most recent address that may have the verification bit set, theverification bit may indicate that the previous write completedsuccessfully. There may be a decision step 214 to determine if the newdata is the same as the previous data. If so, no additional processingsteps may be needed and the process may be done 228. If the data isdifferent from the previous data, there may be a locate and read step230 to determine the next write location for the data. There may beanother decision step 218 to verify that data can be written to the newaddress and word memory. If not, another memory location (additionalwrite depth) must be used to store the new data and a bit is written tothe to the new address 232. This test also allows recovery from a powerfailure during a write operation if this same write operation was leftincomplete due to a previous power failure. There may be a test todetermine if the entire word has been written 220. If the entire wordhas not been written, the step 224 may be to write the next data bit tothe word memory (assuming the data is written one bit at a time). Thelast step 222 may be to set the verification bit to indicate the writeoperation of step 222 was complete.

Again referring to FIG. 1B, in an embodiment, the RFID tag 102 memorymay be implemented using both fixed allocation of memory and dynamicallocation of memory. In this memory configuration, the dynamicallyallocated memory may be implemented as any of the previously describedmethods such as fixed segments with dynamically allocated memory words,dynamically allocated segments with fixed allocation of memory words,dynamically allocated segments with dynamically allocated memory words,or the like. The use of both the fixed and dynamically allocated memorymay provide for information writing flexibility by allowing for users towrite previously undefined information to the RFID tag 102 and to have afixed amount of memory allocated to structured writes of information. Inan embodiment, one implementation of the memory on the RFID tag 102 mayinclude first writing to the dynamic memory and writing to the fixedmemory second. A characteristic of dynamically allocated memory may be alevel of uncertainty of the amount of remaining memory that results fromthe flexibility of the type of information that may be written to thedynamic memory. Using the dynamic memory, users may save informationthat may be of varying lengths and various numbers of records andtherefore may use up the dynamic memory at an unpredictable rate. Anadvantage of implementing writing to dynamic memory before writing tofixed memory may be once the dynamic memory becomes full, and writing tothe fixed memory begins, the RFID tag 102 may return a message to theuser that there is a certain amount of memory remaining to be written.Since the fixed memory has a structured set amount of memory, with everyinformation write to the RFID tag 102, the RFID tag 102 may be able toreturn the amount of memory remaining for additional writes. Forexample, after a write to the RFID tag 102, the RFID tag 102 may returnthe total amount of memory remaining, the remaining write depth of thevirtual address to which information was just written, or the like.

In an embodiment, the RFID tag 102 may implement both OTP and MTP memoryto provide different types of memory regions within the RFID tag 102,the different memory regions may provide different memorycharacteristics to the RFID tag 102. In embodiments, a combination ofthe OTP and MTP memory may be used on all the RF network nodes 104, someRF network nodes 104 may use only OTP memory and some RF network nodes104 may use only MTP memory, or any other combination of OTP and MTPmemory on the RF network nodes 104. The combined OTP and MTP memoriesmay be coordinated to provide read and write capabilities to all of thedifferent regions of memory, all the memory regions may be accessed onthe RFID tag 102 during the same read/write cycle. In embodiments, thedifferent regions of memory may include unlimited writing regions,limited writing regions, once write regions, or the like.

In an embodiment, MTP memory may be used to provide the unlimitedwriting regions of the RFID tag 102. In an embodiment, the MTP memorymay be allocated to some or all of the RF network nodes 104 and may becoordinated by the RF network node 104 architecture to appear as acontinuous memory space to the user. The use of the MTP memory may allowunlimited writing to all the MTP memory locations for the life cycle ofthe RFID tag 102.

In an embodiment, OTP memory may be used to provide the limited writingregions of the RFID tag 102. In an embodiment, the OTP may use any ofthe above described OTP and eMTP memory allocation methods such asdirect mapping, segment mapping, fixed memory word allocation, dynamicword allocation, dynamic segment allocation, or the like. In anembodiment, the limited write region may be implemented using only OTPmemory, MTP and OTP memory, or the like.

In an embodiment, OTP memory may be used to provide the once writewriting regions of the RFID tag 102. In an embodiment, the OTP memorymay be organized into individual memory locations that may allowinformation to be written once to the individual memory location, butread many times. In an embodiment, the once write regions may be used tosave information that should not be changed during the life cycle of theRFID tag 102. For example, it may be advantageous to save a part numberor serial number of an object that the RFID tag 102 is associated withto prevent this information from being over written during the lifecycle of the RFID tag 102. In an embodiment, the once write region mayprovide a form of write protection for information stored within theonce write region.

In an embodiment, the segment table 202 may store pointer informationfor the segment maps 208 for an individual RF network node 104, for aplurality of RF network nodes 104, or the like. In an embodiment, thesegment table 202 may store pointer information for redundant memory,distributed memory, public memory, private memory, or the like.

In an embodiment, an OTP memory location may be written to more thanonce. Information may be written to the OTP memory where the informationdoes not change often, for counters, or the like. In an embodiment,there may be a protocol for storing new data in an OTP memory locationthat may already contain data. For example, a counter may use the samenumbers over time and the numbers that may have previously been used maybe written to again with the same number. A portion of the direct maps204 or segment maps 208 may be dedicated to a counter and the datablocks reused, as the counter is incremented. In another example, thesame information may be written a number of different times (e.g. aproduct name), the information may be checked to determine if theinformation has been previously stored before storing the newinformation.

While many of the embodiments disclosed herein involve multi nodeconfigurations, it should be understood that the OTP, MTP, and eMTPmemory described herein may be used in single RF network node 102 orsingle radio chip RFID tags 102 where the single RF network node orradio chip may have OTP, MTP, eMTP memory individually or incombination. Additionally, the OTP, MTP, eMTP memory described hereinmay also be used in non RFID tag technologies for memory storage.

In an embodiment, a single RF network node 104 RFID tag 102 may includeOTP memory and may store information within the OTP memory.

In an embodiment, a single RF network node 104 RFID tag 102 may includeOTP and MTP memory and may store information within the OTP and MTPmemory.

In an embodiment, a single RF network node 104 RFID tag 102 may includeOTP memory as a one time write memory to emulate MTP memory.

In an embodiment, a single RF network node 104 RFID tag 102 may includeOTP memory, where the OTP memory may use multiple words to storeinformation.

In an embodiment, a single RF network node 104 on an RFID tag 102 maycoordinate OTP memory within the single RF network node 104 RFID tag102.

In an embodiment, an RFID tag 102 may include a single RF network node104 and may coordinate OTP memory using segment tables and directmapping of data related to the segment tables.

In an embodiment, an RFID tag 102 may include a single RF network node104 and may coordinate an OTP direct map using an MTP segment table.

In an embodiment, a single RF network node 104 RFID tag 102 may writeinformation to OTP memory using a fixed write depth.

In an embodiment, a single RF network node 104 RFID tag 102 may writeinformation to OTP memory using a variable write depth.

In an embodiment, a single RF network node 104 RFID tag 102 maycoordinate dynamic allocation of OTP memory.

In an embodiment, a single RF network node 104 RFID tag 104 may use analgorithm to determine if a memory write has completed and may recoverif the write did not complete.

In an embodiment, an RFID tag 102 that includes OTP memory may be usedfor archiving data over long periods of time, such as days, months,years or the like. The archiving of data may include the permanentstoring of information within the non-volatile memory, such as OTPmemory, of the RFID tag 102. For example, in the aviation industry theremay be requirements to maintain data for up to twenty years. Aspreviously described, when new information may be written to OTP memory.In using OTP memory to store information existing information may bemaintained within a memory word and the new information to be stored maybe written to a new memory word, leaving the original information on theRFID tag. In an embodiment, the saving of the original information andstoring new additional data may provide data history that may be used asarchive information where both the new and old information may beretrieved, viewed, read, transmitted to an external network, or thelike. In one embodiment, there may be an interface with the RFID tag 102where the user may be able to view the archived information.

As previously described, the original and new information may be storedin fixed allocated OTP memory, dynamically allocated OTP memory, or thelike. The different write depth memory systems may be used to storearchived information on the RFID tag 102. For example, a fixed writedepth memory may provided for a fixed amount of memory archiving whiledynamically allocated memory may have a variable amount of archivingthat may only be limited by the amount of memory available on the RFIDtag 102.

Additionally, using OTP memory as archiving memory may provide ahardened memory system that resists environmental changes to the storedmemory information such as vibration, temperature, humidity, shock, andthe like. Since OTP memory information is burned into the RFID tag theinformation is non-volatile and may be resistant to environmentalchanges to memory.

In addition to the hardened aspects of the archive OTP memory resistanceto environmental influences, the RFID tag 102 may include a start-upmemory test to determine the availability of memory for storage or ifmemory locations may have received damage that might affect the OTPmemory. In an embodiment, if a blank memory location is determined to bedamaged, the damaged memory locations may be marked to not receiveadditional information. In another embodiment, if a memory that containsinformation is determined to be damaged, the RFID tag 102 may attempt tomove the information from the damaged locations to non-damaged locationswithin the RFID tag 102.

In embodiments, archiving of information on multiple RF network node 104RFID tags 102 may be used for aviation history, medical instrumenthistory, medical patient history, vehicle maintenance history, foodhistory, security history, pharmaceutical history, personalidentification history, and the like.

In an embodiment, the combined memory of the RFID tag 102 may beorganized with more than one memory method. For example, one memorylocation may use a fixed write depth while another memory location mayuse variable write depth. The way in which the RFID tag 102 memory isallocated may be determined by the type of information the RFID tag 102is storing and the memory usage may vary from one RFID tag to anotherRFID tag. In an embodiment, the memory may be allocated as theinformation is stored to the RFID tag 102, when the RFID tag 102 isassociated to an object, when information is first written to the RFIDtag 102, or the like.

In an embodiment, the RFID tag memory organization may be stored in aconfiguration table on the RFID tag. In embodiments, the configurationtable may be stored on a single RF network node 104, stored acrossmultiple RF network nodes 104, or the like. The configuration table maystore and manage data related to the organization of the RFID tag 102memory such as types of memory, memory regions, word depth writing type(e.g. fixed or variable), and the like. In an embodiment, theconfiguration data may be considered metadata for the data writing typeregions of the RFID tag 102. In an embodiment, the configuration tablemay be fixed or dynamic. For example, with a fixed configuration table,the table may be written with the configuration of the available memoryand may not be changed during the life of the RFID tag 102. A dynamicconfiguration table may be able to have different memory allocationswritten to it over time as the memory is allocated. For example variableword depth is used on the RFID tag 102 and as additional word depths aremade available to memory, the new memory region for the variable depthmemory may be stored to the configuration table.

Referring again to FIG. 1, in embodiments, the data processing andcontroller 132 may support a digital adjustment of the impedance matchbetween the antenna 108 and the circuitry of the RF network node 104.The ESD and impedance matching 110 functional block may include multipleswitch elements to turn on or off. In embodiments, the data processingand controller 132 may include a function that results in switchelements being turned on or off. In embodiments, the data processing andcontroller 132 may determine the number of switch elements to turn on oroff in the ESD and impedance matching 110 block. The data processing andcontroller 132 may send more than one control command for the adjustmentof the ESD and impedance matching 110 block. For example, the dataprocessing and controller 132 may read the value of a parameterassociated with the strength of the received signal from the reader 140,and the data processing and controller 132 may send a command to adjustthe switch settings of the ESD and impedance matching 110 block. Thisprocedure may continue until a maximum value for the parameter isreached. Another example may be the data processing and controller 132sending a command to adjust the switch settings of the ESD and impedancematching 110 block after each read attempt by the reader 140.

In embodiments, the data processing and controller 132 may support thereader 140 control of impedance matching. The reader 140 may have analgorithm to receive the RFID tag 102 transmissions, measure thestrength of the response, calculate a command function, and resend theread signal with the command function. The command function may be acommand to adjust the impedance and resend the data. The commandfunction may be received by the data processing and controller 132,which may create the control command to be sent to the ESD and impedancematching 110 block to turn switch elements on or off to match theimpedance of the antenna 108. An improved impedance match may result inthe improved strength of the RFID tag 102 on the second return signal.In embodiments, the process of the reader 140 sending a read request,and a function command to adjust the impedance, may be repeated until anacceptable reception level is achieved.

In embodiments, the data processing and controller 132 may supportcommunications from one RF network node 104 to another RF network node104 across the inter-node interface 154 and the RFID tag's 102 commonantenna connection 158 as will be described in FIG. 5B. The inter-nodeinterface 154 may connect to the common antenna connection 158 throughthe RF network node's 104 ESD and impedance matching block 110. Thecommon antenna connection 158 may connect all of the RF network nodes104 of the RFID tag 102, as well as the RFID tag's 102 antenna(s) 108,together. Data may be transferred across these connections from one dataprocessing and controller 132 to another. The data processing andcontroller 132 of each of the RF network nodes 104 may include atransmitter and receiver in support of this interface. Transmissionacross this interface may be accomplished by modulating the DC level ofthe signal on the common antenna interconnection 158 by using aninverter with a high resistance at its output that is connected to theinterface. In this way, the DC level may be modified (AM modulation). Inembodiments, the data rate across the inter-node interface 154 may be ata relatively low rate, such as 75 kHz, 100 kHz, 150 kHz, or the like, ascompared with the HF and UHF frequencies of the reader's 140 carrierwave.

The configuration for the inter-node interface 154 and the commonantenna connection 158 may be any one of a plurality of interfaceinterconnections known to the art, such as a series bus, a parallel bus,a series daisy-chain, and the like. In embodiments, the interconnectionof the inter-node interface 154 and the common antenna connection 158may be made through the ESD and impedance matching block 110.Communications across the inter-node interface 154 may occursimultaneously with, or exclusive from, transmissions to and from thereader 140 or other tags. In embodiments, capacitance on the commonantenna connection 158 may be such that the communication's bandwidthremains sufficient for both the low frequency of inter-node interfacecommunications, a frequency of 100 kHz for instance, and the highercarrier frequency of the reader 140, a frequency of 900 MHz forinstance.

In embodiments, the data processing and controller 132 may have aninternal data bus 530 that enables communication within the dataprocessing and controller 132. This internal data bus 530 may provide adirect data path between processing elements, memory, registers,arithmetic units, and the like. The internal data bus 530 may providebuffered data paths between the data processing and controller 132 andfunctional blocks that are external to the data processing andcontroller 132, such as the random number generator 122, the persistence124 circuit, the modulator 128, the demodulator 118, the communicationsfacility 134, and the like.

In embodiments the master RF network node 104 may control thecommunication's path between the RF network nodes 104, which includesthe internal data bus 530, the inter-node interface 154, and the commonantenna connection 158. The master RF network node 104 may utilize thiscollective communications path for a plurality of cross-RF network node104 functions, such as shared or distributed memory, shared ordistributed processing, redundancy management, master RF network node104 protocols, or the like.

In embodiments, the data processing and controller 132 may includeprogramming, logic, and/or memory in support of a function fordetermining which of the RF network nodes 104 may be the master RFnetwork node 104 on the RFID tag 102. The master RF network node 104determination may occur each time the RFID tag 102 is powered up.Alternately, the master RF network node 104 assignment, onceestablished, may be maintained during brief interruptions in power bystoring the assignment logic state in the persistence 124 circuitry,described herein. Assignment of the RF network node 104 as master orslave may also be stored in memory, where memory may be volatile for useduring operations, or non-volatile for use over multiple operational,power on/off periods. The data processing and controller 132 function,that performs the selection of the master RF network node 104, mayutilize the random number generator 122. The data processing andcontroller 132 may control the random number generator 122 by providinga logical enable signal, generate a random number signal, read a randomnumber signal, or the like. There may be a data interface between therandom number generator 122 and the data processing and controller 132,which may be a serial or parallel interface. In embodiments, theinterface may be a serial interface, reading an exclusive-or of themultiple oscillators running in the random number generator 122.

In embodiments the reader 140 may be connected to computer device 202(as shown in FIG. 2). The computer device 202 may be a server, a desktopcomputer, a laptop computer, a tablet computer, a handheld computer, asmart device (e.g. a smart phone), or the like. Additionally, thecomputer device 202 may be connected to a network 152 for support ofadditional functionality that may include data storage 144, anapplication server 148, the markets 150, or the like. In an embodiment,the network 152 may be a LAN, WAN, peer-to-peer network, intranet,Internet, or other network system.

The computer device 202 may provide support to the reader 140 byproviding the commands for the reader 140 to transmit to the RFID tags102. The computer device 202 may be used as a temporary store for theinformation received by the reader 140 from the RFID tags 102 to whichthe reader 140 is communicating. The temporary store of the computerdevice 202 may aggregate the RFID tag 102 information until all theinformation is transmitted, then the information may be transmitted tothe network 152. The computer device 202 may transmit the information tothe data storage 144, the application 148, the market 150; may make theinformation available for the data storage 144, the application 148, themarket 150 to retrieve as needed; or may separate the aggregatedinformation into individual information for the data storage 144, theapplication 148, the market 150.

The data storage 144 may include a data storage medium (e.g. disk drivesand memory), computer devices, servers, or the like. The data storage144 may be for an individual enterprise to store information from thereader 140, storing information for a plurality of enterprises from thereader 140, or the like. In an embodiment, the application servers 148and the markets 150 may store and retrieve information from the datastorage 144.

The application servers 148 may be used to aggregate information fromthe reader 140 over the network 152 for an individual enterprise, for aplurality of enterprises, of entire markets 150, or the like. Theapplication servers 148 may receive or retrieve raw information from thereader 140 and computer device 202 and perform information conversion,information aggregation, information segregation, or the like that maybe used for reporting, alerting, or the like. For example, theapplication server 148 may aggregate the movement information of aproduct from the plurality of readers 140 over the products distributionsystem. The application server 148 may create an aggregated report onthe total movement of the product from the start of the distribution toits present location. Additionally, the application server 148 may sendout an alert to an enterprise if it is determined that a product hasremained at a single location longer that is necessary. For example,where the product may be a perishable product and is required to bedelivered to a market within a certain time period, the applicationserver 148 may provide an alert that the delivery is being held up at aparticular location so the enterprise may intervene to ensure its timelydelivery.

As depicted in FIG. 1, markets 150 may include entire segments of theeconomy such as food management, retail general merchandise, retailservice stations, retail physical plants, retail hotel and resorts,restaurant food service, employee identification, security systems,airline services, marine and shipping, office systems, communicationsystems, public event services, and the like. It would furthermore beapparent to someone skilled in the art that the RFID tags 102 asdescribed herein may be used in many different markets and that thislist is not to be considered as a limiting list; instead, any marketswhere the RFID tags 102 as described herein may be used are to beconsidered consistent with the systems and methods described herein. Anexemplary set of markets 150 will be described further herein. In anembodiment, markets 150 may access the network 152 to receiveinformation, retrieve information, transmit information, or the like. Inembodiments, markets 150 may retrieve or receive information from theapplication servers 148, data storage 144, computer devices 202, readers140, or the like. In embodiments, markets 150 may use the data storage144 or application servers 148 to aggregate, separate, collect, or thelike data from the reader 140 or the markets 150 may perform their owninformation aggregation, information separation, information collection,or the like. Markets 150 may also transmit information to the computerdevices 202, readers 140, and application servers 144. For example, amarket 150 may transmit information to the reader 140 to retrievecertain information from an object when the reader 140 reads the objectsRFID tag 102.

FIG. 2 shows schematically the overall architecture of the RFID tag 102,and how it may interact with the surrounding system. In embodiments, theRFID tag 102 may include the plurality of RF network nodes 104, theplurality of antennas 108, the common antenna connection 158 that tiesRF network nodes 104 together and to the antenna(s) 108, the inter-nodeinterface 154 that enables communication between the RF network nodes104, the communications facility 134, a gateway interface 160 betweenthe communications facility 134 and the external sensors 138, and thelike. The RFID tags 102 may communicate externally with the reader 140,with other RFID tags 102 by way of the RFID tag's 102 antennas 108, orwith the external sensors 138 by way of the RFID tag's 102communication's facility 134. The RF network nodes 104 may alsocommunicate internally with each other across the signal interface,which may include the inter-node interface 154 and the common antennaconnection 158, connecting the RF network nodes 104 to each other and tothe RFID tag's antenna(s) 108. In addition, the markets 150 being servedby the RFID tags 102 may have a connection into the RF network node's104 data processing and controller 132 by way of embedded market 150application specific logic, programming, memory, or the like.

FIG. 3 shows an embodiment of the overall architecture of the RF networknode 104. In embodiments, the RF network node 104 may be represented bythree functional blocks: the RF and analog 302 block, the dataprocessing and controller 132 block, and the power management 130 block.External interfaces to these functional blocks within the RF networknode 104 may include the antenna 108, the communications facility 134,markets 150, and the like. In embodiments, the external interface to themarkets 150 may not be a direct physical connection, but may insteadrepresent an application connection that may be realized at the deviceprogramming and/or configuration stage, at the manufacture of thedevice, or as a part of operational reading and writing fromnon-volatile memory (e.g. EEPROM or Flash memory for instance) throughthe antenna 108, and on through the reader 140 and the network 152 tothe markets 150. In embodiments, the interface to the communicationsfacility 134 may be an analog interface, a serial or parallel digitalinterface, or any signal communications interface known to the art. Inembodiments, the communications facility 134 may be a gateway for aplurality of external facilities 138 that are described herein.

FIG. 3 further depicts the internal communication paths between thethree functional blocks, including transmit, receive, and controlsignals between the RF and analog block 302 and the data processing andcontroller block 132, as well as power and control signals between thepower management 130 and the RF and analog 302 and the data processingand controller 132 blocks. In embodiments, a typical operation for theRFID tag 102 with the plurality of RF network nodes 104 may be thereception and execution of a command from the reader 140. Upon receptionof a continuous RF carrier wave from the reader 140, the RF networknodes 104 may extract power from the impinging RF carrier wave to supplypower to the RF network node 104. Extracting power from the impinging RFcarrier is also referred to as harvesting power from the RF carrier.Maximizing the harvested power from the RF carrier wave may be achievedby providing the optimum impedance match between the antenna 108 and theRF network node 104. In embodiments, the impedance matching may be adynamic process controlled through analog or digital circuitapplications.

FIG. 4 provides a flow chart depicting one possible scenario for theRFID tag 102 receiving and executing a generic command from the reader140, as previously described with reference to FIG. 1. The flow graphbegins with the start of a data read 402 sequence, where the readertransmits a modulated carrier 404 to the RFID tag 102 within range. Theantenna 108 receives the carrier wave, and power from the carrier waveis rectified and filtered in the power management 130 block at sequence408. The power management block 130 circuitry may sense whether there issufficient power to power up 410 circuitry within the RF network node104. If not, there may be analog circuitry that changes an impedancematch 412 between the receiving circuitry and the antenna 108 untilsufficient power levels are achieved. When there is sufficient power,the power management 130 block powers up circuitry 414 in the RF andanalog block 302 and the data processing and controller block 132. Oncethere is sufficient power to power up the circuitry on the RF networknode 104, there may be a step where the data processing and controllerblock 132 executes a routine for impedance matching to adjust formaximum power 418. Once optimum impedance matching has been achieved,the incoming signal may be demodulated in the RF and analog block 302,and a digitally converted command is read 420 by the data processing andcontroller block 132.

In the RFID tag 102 where there is more than one RF network node 104, asdescribed above with reference to FIG. 2, a protocol 422 to select themaster RF network node 104 may be utilized to determine which RF networknode 104 may be the master 424 for the execution of command and controlof the received commands. If at least one of the RF network nodes 104 isdetermined to not be the master, it may enter a slave mode 428. If theRF network node 104 is determined to be the master, a received commandmay be executed 430 by the master RF network node 104. After commandexecution, the response to the command may be formatted by the dataprocessing and controller 132 block and sent to the RF and analog block302 to be modulated 432 and transmitted 434 to the reader 140. When thereader 140 receives the data 438, the reader 140 may terminate thetransmitted carrier wave 440, which in turn may remove the source ofpower from the RFID tag 102. The RFID tag 102 may then power down 442.The data read sequence may then be ended 444. It should be understoodthat this flow graph, representing one possible sequence that may beexecuted by the RFID tag 102, is provided as a representative routine toillustrate the operability of some of the major functional blocks of theRFID tag 102, and is not meant to limit the functional capabilities ofthe RFID tag 102, as illustrated by embodiments described herein.

In the above protocol, the first RFID tag 102 component to be physicallyacted upon may be the antenna 108. However, as shown in FIG. 2, theremay be multiple RFID tags 102, each with multiple antennas 108. Oneantenna 108 may be connected to multiple RF network nodes 104; multipleantennas 108 may be connected to a single RF network node 104 or tomultiple RF network nodes 104; one antenna 108 may be connected to oneRF network node 104 or multiple RF network nodes 104, while anotherantenna 108, on the same tag 102, may be connected to a separate RFnetwork node 104 or multiple RF network nodes 104. In the case wherethere is more than one antenna 108 connected to the RF network node 104,or multiple RF network nodes 104, the RFID tag 102 may select whichantenna 108 is to be used in communications. In addition, differentantennas 108 may be optimized for different frequencies, such as oneantenna 108 operating at high frequency (HF) while another antenna 108is operating at ultra high frequency (UHF), very high frequency (VHF),or the like. The individual antenna 108 may also be capable of receivingand transmitting signals on different frequencies. The antennas 108 maybe transmitting and receiving with the reader 140 or other RFID tags102. In embodiments, if the ESD and impedance matching 110 schemeutilizes capacitive impedance, the antennas 108 may need to havepositive real impedance for best results.

In embodiments, the connection of multiple antennas 108 with multiple RFnetwork nodes 104 may be associated with an electrical reference ground532. FIG. 5A shows four antenna interconnection configurations 500A-D ofa plurality of possible combinations of antennas 108 and RF networknodes 104. For example, FIG. 5A shows an antenna interconnectionconfiguration 500A where four antennas 108 are interconnected with fourRF network nodes 104. In embodiments, each antenna 108 may be connectedto an RF network node 104, as well as connected to the other antennas108 and other RF network nodes 104. Further, power may be receivedprimarily by the antenna 108 most directly associated with the RFnetwork node, or may be shared amongst the interconnected RF networknodes 104. For example, energy received by the antenna 108A may beprimarily used by the RF network node 104A, or may be shared by some orall of the interconnected RF network nodes 104A-D. In an embodiment, foreach of the four antenna interconnection configurations 500A-D, theremay be a third connection point on the RF network node 104, in additionto the two antenna 108 connection points, connected to the commonelectrical reference ground 532. The common electrical reference ground532 may provide the electrical reference for power and signals on andbetween the RF network nodes 104, and thus provide a common electricalreference ground 532 for multiple RF network nodes 104 on the RFID tags102.

In embodiments, each antenna 108 may be paired with a specific RFnetwork node 104. An antenna 108/RF network node 104 pair may beinterconnected with other antenna 108/RF network node 104 pairs, or maybe separate. For example, the antenna interconnection configuration 500Dshows two antenna 108E-F/RF network nodes 104E-F connected together, andone antenna 108G/RF network node 104G separate. In embodiments, antenna108/RF network node 104 pairs that are connected together may sharepower. For instance, the antenna 108E/RF network 104E pair is connectedto antenna 108F/RF network 104F pair, and there may be circuitry on theRF network node 104 that enables them to share, or redirect, powerreceived by the antennas 108E-F to the associated RF network nodes104E-F. In embodiments, the sharing circuitry may include a method tologically-or the connections from multiple antennas 108 to the RFnetwork node 104. Further, this sharing circuitry may provide a methodto reduce the amount of power received by a given RF network node 104.

The embodiments shown in the antenna interconnection configurations500A-D show examples that include one antenna 108 for each RF networknode 104. In embodiments, other configurations may include one antenna108 for a plurality of RF network nodes 104, a plurality of antennas 108for each RF network node 104, or other configuration ratio of antenna108 to RF network node 104; there may be many different configurationsfor a plurality of antenna 108/RF network node 104 combinations. Aperson skilled in the art may understand that the may be other antenna108 and RF network node configurations. The embodiments shown areprovided as examples of antenna 108/RF network node 104 configurationsand should not be considered limiting.

FIG. 5B shows the interconnection between the ESD and impedance matching110 circuitry of two RF network nodes 104. In embodiments, the ESD andimpedance matching 110 circuitry may include three connections, twoconnections that include the common antenna connection 158, and oneconnection to the common electrical ground 532. In embodiments, thecommon antenna connection 158 may provide a path for power received fromthe antenna 108 to the RF network node 104, a path for reader 140to/from RF network node 104 communications, a path for RFID tag 102 toRFID tag 102 communications, a path for RF network node 104 to RFnetwork node 104 communications, and the like. In embodiments, thecommon electrical ground 532, connected to all the RFID tag's 102 RFnetwork nodes 104, may provide the electrical ground reference for thesepower and communications interconnections.

In embodiments, the RF network node 104 may utilize the inter-nodeinterface 154, and the associated common antenna connection 158, in thecommunication with other RF network nodes 104 during execution of themaster RF network node 104 determination function, as previouslydescribed with reference to FIG. 2. An embodiment of the RF network node104 using the random number generator 122, the inter-node interface 154,and associated logic, is shown in FIG. 5B. Upon initial power up of theRF network nodes 104 on the RFID tag 102, and after impedance matchinghas been achieved, the RF network nodes 104 may each read a value fromtheir random number generator 122, and write the value into a memoryregister 524. Additionally, the RF network nodes 104 may present thevalue from the random number generator 122 to the inter-node interface154 through a buffered 520 output. In embodiments, the RF network nodes104 may be performing this function at different times, as describedherein, where the first RF network node 104 to present a random numberonto the inter-node interface 154 may get its value written into a busregister 522 of all the RF network nodes 104 on the RFID tag 102.

With the first RF network node's 104 random number written into the busregister 522, and each of the RF network nodes 104 eventually writingits own random number into its memory register 524, as depicted in FIG.5B, the RF network node 104 may now determine if it is the master RFnetwork node 104. Each of the RF network nodes 104 may compare 528 thecontents of the memory register 524 and the bus register 522. If thevalues in the RF network node's 104 memory register 524 and the busregister 522 are the same, then it may be selected as the master. Ifnot, it may be a slave. In the case where two or more of the RF networknodes 104 are simultaneously writing their random number out onto theinter-node interface 154, the value written into the bus registers 522of all of the participating RF network nodes 104 may be a combination ofall the random number values placed on the inter-node interface 154, andthus represent neither of the RF network node's 104 value from itsrandom number generator 122. In this instance, no RF network node 104may be immediately selected to be the master RF network node 104, andother protocols, described herein, may be required to resolve themismatch of the random number on the bus registers 522. It may beunderstood that these examples illustrate only one of a plurality ofhardware/software configurations to implement the master RF network node104 determination function, and that other implementations will beunderstood by one skilled in the art.

In embodiments, described with reference to FIGS. 1 and 2, the master RFnetwork node 104 may provide configuration management for the RFID tag102, such as switching the antennas 108, switching the antenna 108frequency, configuring the communications facility 134, and the like.Configuration management may be dictated by external control, viacommanding through the reader 140 interface or from another RF networknode 104. Configuration management may be self directed by the master RFnetwork node 104, through programming, through stored tables in memory,or the like. Configuration management may be associated with redundancymanagement, where the master RF network node 104 may be configuring theRFID tag 102 to maintain an optimum operational configuration.

In embodiments, described with reference to FIGS. 1 and 2, the dataprocessing and controller 132 may provide for redundancy management ofthe elements within its own RF network node 104, and for the RF networknodes 104 and the antennas 108 on the RFID tag 102, as well as for otherRFID tags 102. The master RF network node 104 may execute redundancymanagement. A plurality of elements may be managed with respect toredundancy, such as individual RF network node 104 functional blockssuch as an oscillator 120, the random number generator 122, thepersistence circuit 124, memory, and the like, or the RFID tag 102elements such as the antennas 108 and the communication facility 134.Redundancy management may also extend to other RFID tags 102 in thearea.

In embodiments, described with reference to FIGS. 1 and 2, the master RFnetwork node 104 may provide for redundancy management of the pluralityof RF network nodes 104 on a the RFID tag 102. The RF network nodes 104may be assigned redundant roles at the time of manufacture; duringoperations, as failures are encountered; changed over time; or the like.The master RF network node 104 may systematically store functionalmemory in multiple locations, on the multiple RF network nodes 104, inpreparation of eventual RF network node 104 failures on the RFID tag102. In the event of the RF network node 104 failure, the master RFnetwork node 104 may reconfigure the RFID tag 102 functionality to workaround the failure. Such reconfiguration may lead to a restoration offull functionality, lead to a transition back to full functionality,lead to degraded functionality, or the like. The master RF network node104 may assign one of the secondary, or slave, RF network nodes 104 as abackup to the master RF network node 104, which may assume the role ofthe master RF network node 104 in the event of a failure of the primarymaster RF network node 104. In embodiments, the master RF network node104 may report failures to the reader 140 that may access the RFID tag102. In embodiments, the RFID tag's 102 functionality may be reduced bythe failure, and this reduction in functionality may be reported to thereader 140 that accesses the RFID tag 102. The ability of the RFID tag102 to self-monitor, manage redundancy, and report failures, may improvethe reliability of the device, especially in harsh environments that areprone to causing physical damage to the RFID tags 102.

Moreover, in an embodiment, the depicted RFID tag 102 may be able toreport the status of the RF network nodes 104 in the RFID tag 102. Thismay allow for advance notice of a potential permanent disablement of theRFID tag 102, which can be then used to take appropriate remedialactions. For example, the RFID tag 102 may contain four RF network nodes104, but two may have become damaged and the remaining two RF networknodes 104 may be providing redundant functionality or memory; thedamaged RF network nodes 104 may reduce the over all functionality ofthe RFID tag 102. The RFID tag 102 may communicate in a transmission tothe reader 140 that there are damaged RF network nodes 104 and that theRFID tag 102 functionality may be reduced. This may provide advancenotice to replace the RFID tag 102 to restore full functionality andinformation recording.

In embodiments, the master RF network node 104 may provide forredundancy management of the antennas 108 resident on the RFID tag 102.The master RF network node 104 may monitor performance characteristicsof all the antennas 108 on the RFID tag 102, such as received signalstrength, impedance, transmitted signal strength as reported back fromthe reader 140, and the like. The master RF network node 104 may selectthe antennas 108 that may be performing best, and report a status of theantenna 108 performance to the reader 140.

In embodiments, the master RF network node 104 may provide the RFID tag102 with functional redundancy to guard against the possibility of anentire RFID tag 102 failing, or degrading below an acceptable functionallevel. To accommodate this, the master RF network nodes 104 fromdifferent RFID tags 102 may communicate with each other, and providefunctional redundancy of their operational memory space. Further, themaster RF network nodes 104 may periodically communicate with nearbyRFID tags 102 to assess the health of these RFID tags 102. In the eventthat one of these communications were to fail, or indicated reducedfunctionality, the next RF network node 104 may take over the operationspreviously assigned to the failed RFID tag 102.

In embodiments, the data processing and controller 132 may provide forthe logging of transactional information, such as commands received,actions taken, sensors 138 read, processes completed, and the like.Logging of the transactional information may be recorded in memory as arunning table, time-tagged, priority-tagged, subject-tagged, and thelike. The transactional information may be searched, sorted, or read inassociation with tagged information. A dump of the transactional log maybe initiated by command, performed periodically, performed each time theRFID tag 102 is powered, and the like. The logged transactionalinformation may be monitored and compared to standard parameters, andactions taken, or status provided, if those parameters are met, not met,exceeded, or the like. The ability to log the transactional informationmay enable the market 150 applications to better monitor the activity ofthe RFID tag 102.

The data processing and controller 132, as depicted in FIGS. 1 and 2,may provide the gateway interface 160 to the sensors 138 through thecommunications facility 134. In embodiments, the interface between thedata processing and controller 132 and the communications facility 134may be associated with a buffered 520 connection to the data processingand controller 132 internal bus 530, as shown in FIG. 5B. The interfacebetween the communications facility 134 and the sensors 138 may supporta plurality of electrical interface types, including serial digital,parallel digital, analog, voltage source, current source, differential,or the like. The communications facility 134 may be associated with thesensor 138A signal conversion from serial digital to parallel digital,parallel digital to series digital, analog to digital, digital toanalog, or the like. The sensors 138 may be any of a plurality oftransducers, such as temperature, humidity, motion, CO, CO2, moisture,smoke, pressure, light, vibration, and the like. Although FIGS. 1 and 2both refer to the communications facility 132 interfacing with sensors138, it is understood that sensors 138 is a general term, and may alsoinclude a plurality of external facilities and interfaces, such asexternal memory and USB, Ethernet, WiFi, Zigbee, and the like,interfaces. The ability of the RFID tag 102 to interface with thesensors 138 may significantly increase its market 150 functionality andusefulness.

In an RFID tag 102 that contains multiple RF network nodes 104, asdepicted in FIG. 2, certain embodiments may involve the determination ofa master RF network node 104 to coordinate the activities of the otherRF network nodes 104 on the RFID tag 102. In an embodiment, the masterRF network node 104 may manage the RFID tag 102 distributed memory,manage the redundancy of the RF network nodes 104, receiving informationfrom the reader 140, transmitting information to the reader 140, or thelike. In an embodiment, the RF network nodes 104 may have acommunication connection that permits the individual RF network nodes104 to communication information. Once a master RF network node 104 hasbeen determined, the other RF network nodes 104 may act as slave RFnetwork nodes 104 to the master RF network node 104.

In an embodiment, there may be a number of configurations of RF networknode 104 connections that would provide for the determination of amaster RF network node 104, such as a serial connection between RFnetwork nodes 104, a parallel connection between RF network nodes 104,an antenna connection between the RF network nodes 104, or the like. Inan embodiment, the connection between the RF network nodes 104 may beimplemented by individual RF network nodes 104 connected with leads,physically connected RF network nodes 104 combined into a single largerRF network node, or the like. FIG. 5C relates to the determination of amaster RF network node 104 in either a serial or parallel connection ofthe RF network nodes 104; the RF network nodes 104 may be connected byleads or may be physically connected. The master RF network node 104 maycontrol the function of all the RF network nodes 104 of the RFID tag102. The master RF network node 104 may determine the memory locationsfor certain data, the broadcast time slot for the RF network nodes,additional function connections, and the like.

In an embodiment, the functions of the RFID tag 102 may be controlled bya single RF network node 104 (master RF network node 104) within theRFID tag 102. In embodiments, the master RF network node 104 may be anyof the individual RF network nodes 104 within the RFID tag 102. Asdiscussed further below, there may be a selection protocol fordetermining which individual RF network nodes 104 may become the masterRF network node 104.

In an embodiment, a plurality of RF network nodes 104 may be connectedtogether in a serial or parallel manner; FIG. 5C shows an embodiment ofa serial connection.

Referring to FIG. 5C, an exemplary protocol for determination of amaster RF network node 104 in a multiple RF network node 104 RFID tag102 may be described. In the depicted embodiment, there may be a numberN of individual RF network nodes 104 in the RFID tag 102. In thisembodiment, all of the N RF network nodes 104 may contain identicalfunctional capabilities. A protocol for determining which RF networknode 104 may become the master RF network node 104 may involve thefollowing steps. First, each individual RF network node 104 receives alogical setting from the previous individual RF network node 104. All ofthe individual RF network nodes 104 may be connected by a common powerlead 504. All of the individual RF network nodes 104 may also contain alogical lead 510 that may be connected to the previous individual RFnetwork node 104 or may be connected to another logical RF network node104 or another function network node. In the depicted embodiment, eachindividual RF network node 104 within the RFID tag 102 may sense fromits logical input lead 510 if there is an open or closed circuit on thelead 510 connection.

According to this protocol, if the logic lead 510 is open it mayindicate that a previous RF network node 104 is not the master RFnetwork node 104. The open logic lead 510 may indicate to a next RFnetwork node 104 that it should attempt to function as the master RFnetwork node 104. An open logic lead 510 may indicate that the RFnetwork node 104 may be the first RF network node 104 in the line orthat the previous RF network node 104 may be incapable of acting as themaster RF network node 104. Any particular RF network node 104 may notbe capable of being the master because of damage to the RF network node104, damage to the lead 510, not programmed to be the master RF networknode 104, or the like.

According to this protocol, if the logic lead 510 is closed, it mayindicate that the previous RF network node 104 is the master RF networknode 104 and that the next RF network node 104, and additional RFnetwork nodes 104, should act as slave RF network nodes 104 to anycommands transmitted by the master RF network node 104. In anembodiment, the closed logic lead 510 setting between two RF networknodes 104 may be communicated to the other RF network nodes 104. Forexample, if the logical lead 510 is closed between the first and secondRF network nodes 104, the closed logical lead setting may be transmittedto a third RF network node 104 and all the other RF network nodes 104 onthe RFID tag 102.

In an embodiment, the determination of which RF network node 104 is themaster RF network node 104 may cascade down all N RF network nodes 104until a master RF network node 104 is determined or that no RF networknode 104 is determined to be a master RF network node 104. In anembodiment, the determination whether a first RF network node 104 is tobecome the master RF network node 104 may be determined in the logic 512of the first RF network node 104. If the first RF network node 104 iscapable of functioning as a master RF network node 104, the logic 514 ofthe RF network node 104 may close the logic lead 510 circuit to thesecond RF network node 104 to indicate that it is the master RF networknode 104. If the first RF network node 104 is not able to function asthe master RF network node 104, the logic lead 510 circuit may remainopen, indicating that the next RF network node 104 in line shouldattempt to be the master RF network node 104. In this manner, the masterdetermination process may proceed to each RF network node 104 in theRFID tag 102 until a master RF network node 104 has been determined.

In an embodiment, this process may be considered a fail-safe master RFnetwork node 104 selection method because each RF network node 104 inthe RFID tag 102 may be capable of being the master RF network node 104.In an embodiment, as long as one RF network node 104 is functional, amaster RF network node 104 may be determined.

In an embodiment, in addition to the common power 504 and logic leads510 between the RF network nodes 104, there may be other connections asdescribed below in FIG. 20 such as other functional connections, serialbus connections, parallel bus connections, or the like. In anembodiment, the determination of the master RF network node 104 may besubstantially the same in these connection methods.

Another embodiment of a master RF network node determination in amultiple RF network node sub-system is shown on FIG. 7A, FIG. 7B, andFIG. 8. An arbitration and synchronization protocol in a RF network nodemulti-RF network node environment may be used to control the operationof non-attached RF network nodes on the same RFID tag. The master RFnetwork node may be selected through a process of sending asynchronization signal, transmitting a random number seed signal,transmitting a completion of the synchronization, and the like. Theother non-master RF network nodes may use the transmitted random numberseed signal for any functions the RF network nodes may require such asbroadcast time slot determination.

As described above, there may be a plurality (i.e. two or more) of RFnetwork nodes on an RFID tag (e.g. passive or active) connected toantenna leads of the RFID tag. The plurality of RF network nodes may berandomly placed on the antenna lead zone and may randomly connect to theantenna leads. In embodiments, not all of the RF network nodes appliedto the antenna lead zone may make a connection to the antenna leads. Inan embodiment, all of the RF network nodes on the RFID tag may be thesame type of RF network node or there may be more than one RF networknode type on the RFID tag. In an embodiment, the master RF network nodemay be any one of the RF network nodes on the RFID tag and the master RFnetwork node may coordinate the transmissions and activities of theother RF network nodes on the RFID tag.

Another exemplary protocol for determining a master RF network node 104may involve the individual RF network nodes 104 communicating using theantenna 108 as a communication bus. Referring to FIG. 6, an embodimentof a RF network node 104 connection to an antenna 108 as a communicationbus for determination of a master RF network node 104 is shown. Aspreviously described, there may be a plurality of RF network nodes 104connected to a single or multiple antennas 108; the plurality of RFnetwork nodes 104 may be able to communicate using the antenna 108. Inan embodiment, any of the plurality of RF network nodes 104 on an RFIDtag 102 may be a master RF network node. The antenna leads and theantenna 108 may provide a connection between each of the plurality of RFnetwork nodes 104 and the antenna 108 may act as communication bus tothe connected RF network nodes 104. In an embodiment, the plurality ofRF network nodes 104 connected to the antenna 702 may use the antenna108 as a communication path between the plurality of RF network nodes104, thereby permitting the plurality of RF network nodes a method ofinter-communication. The RF network nodes 104 may communicate data onthe antenna bus to support RFID tag 102 capabilities such as coordinateddata backscattering, improved signal strength, flexible data storage,security, reliability, power-efficient system, and the like. In anembodiment, because of the different communication frequencies used, theantenna 102 may be able to act as a communication bus between theplurality of RF network nodes 104 and broadcast information from theRFID tag 102 without the inter-RF network node communication interferingwith the broadcast information.

In an embodiment, a RF network node 104 may include an ESD and impedancematching facility 110, an RF section and demodulation facility 302, aninter-RF network node communication circuit 132, and other logiccircuits for data storage and transmission.

As previously described, the ESD and impedance matching facility 110 mayprovide electro-static protection for the RF network node 104 andimpedance matching between the antenna 108 and RF network nodes 104. Theimpedance matching facility 110 may receive commands to switch elementson/off within the RF network node 104 to improve the impedance matchbetween the antenna 108 and a RF network node 104.

As depicted in FIG. 6, the RF section and demodulation facility 302 mayreceive 622 and transmit 612 data for the RF network node 104 (notshown) to and from the antenna bus (not shown). The RF and demodulationfacility 302 may demodulate the received data signal 622 from theantenna bus and may provide input to the RFID clock 620 for transmissiontiming of the RF network node 104 transmissions.

The inter-node communication circuit 132 may contain an amplifier 638for the amplification of the received information; the amplifiedreceived information may be received information from the antenna bus.In an embodiment, the amplified information may be transmitted to a dataprocessing unit that may be part of the RF network node 104, describedin previous figures. In an embodiment, the inter-node communicationfunctionality described herein may be included as part of the RF sectionand demodulation facility 302.

In an embodiment, as described in FIGS. 1 and 2, the plurality of RFnetwork nodes 104 accessing the antenna bus may provide a distributedfunctionality for the RFID tag 102 with a master RF network node 104coordinating the functionality of the other RF network nodes 104 on theRFID tag 102. The distributed functionality may include combined memorylocations, separate multiple memory locations, secure memory locations,public memory locations, multiple frequencies, selective powerreduction, encryption, decryption, and the like.

In an embodiment, the determination of a master RF network node on anRFID tag 102 may occur during the power up of the RFID tag. Withreference to FIGS. 1 and 2, the power up may, for example, be inresponse to an RFID tag reader 140 requesting the RFID tag 102 tobroadcast information. There may be a period of time during the RFID tag102 power up that may be used for the determination of a master RFnetwork node. In an embodiment, with each power up, a different RFnetwork node 104 may be selected to become the master RF network node104. In an embodiment, there may be a protocol sequence to determinewhich of the plurality of RF network nodes 104 would become the masterRF network node 104.

Referring to FIG. 7, a simplified protocol sequence for determining amaster RF network node is shown. In an embodiment, a RF network node104, as described in FIG. 2, attempting to become a master RF networknode may transmit information to the antenna bus such as asynchronization signal 724, wait periods 728 and 732, a random numberseed 730, a complete signal 734, and the like. In an embodiment, duringthe RFID tag 102 power up, each RF network node 104 may attempt totransmit the random number seed 730 to the antenna bus for the other RFnetwork nodes 104 to read. In an embodiment, the RF network nodes 108may use the new random number seed 730 to determine functions such astransmission time slot for synchronization of operation, encryption,decryption, security, combined memory function, frequency selection orthe like.

In an embodiment, the master RF network node transmission signal mayconsist of a plurality of equal time period signals for the transmissionof information. For example, the time period for the synchronizationsignal 724, completion signal 734, and wait signals 728 and 732 may beof equal length. In an embodiment, as will be discussed in greaterdetail below; the synchronization signal may be used to indicate that amaster RF network node is transmitting a random number seed 730. Therandom number seed signal 730 may be an integer multiplier of the timeperiod of the equal time periods (e.g. start, completion, or wait). Inan embodiment, this may provide for equal length time periods for themaster RF network node transmission signal, the equal length periodsignal may provide for simple master RF network node transmissiondetection. The total master RF network node transmission signal lengthmay be:

TotalSignal periodM=TSync+TWait(#of Waits)+TRandom Number+TComplete

-   -   Where TPeriod=TSync=TWait=TComplete    -   And TRandom Number=TPeriod(# Random number bits)

In an embodiment, as shown above, the time period for the transmissionof the random number seed 730 may be a period equal to any of thesynchronization 724, wait 728 and 732, or complete 734 signals times thenumber of bits in the random number seed 730. Therefore, the randomnumber seed 730 transmission period may be a multiple of any of thesynchronization 724, wait 728 and 732, or complete 734 signal periods inthe signal.

In an embodiment, the master RF network node transmission signal may beof a variable length.

In an embodiment, when an RFID tag 102 receives a power up signal, theplurality of RF network nodes 104 may attempt to become the master RFnetwork node. With the power up signal, all of the RF network nodes 104may attempt to transmit the synchronization signal 724; the individualRF network nodes 104 may transmit the synchronization signal 724 at atime determined by the random number. In an embodiment, the plurality ofRF network nodes 104 may transmit their synchronization signals 724 indifferent time slots, therefore avoiding transmission collisions.

In an embodiment, when the first RF network node 104 transmits asynchronization signal 724, the remainder of the RF network nodes 104 onthe RFID tag 102 may refrain from transmitting and may read the randomnumber seed signal 730 that has been transmitted to the antenna bus. Ina non-collision situation, only one RF network node 104 may transmit thesynchronization start signal 724 to the antenna bus. Once one RF networknode 104 has transmitted a synchronization signal 724, it may thentransmit a random number seed 730 onto the antenna bus that the other RFnetwork nodes 104 may then read. The other RF network nodes 104 may usethis new random number to determine the transmission time slot forbackscattering data or other RF network node 104 function.

In an embodiment, with all of the RF network nodes 104 using the samerandom number seed 730, all of the RF network nodes 104 may transmittheir information at the same time or at a time determined by the use ofthe random number seed 730. In an embodiment, this may allow for thestorage of the same information on the plurality of RF network nodes,coordination of information storage across a plurality of RF networknodes 104, or the like. In an embodiment, this may enable the pluralityof RF network nodes 104 to act as a single large memory location withdifferent RF network nodes 104 storing different information.

In an embodiment, there may be more than one type of RF network node 104on the RFID tag 102; in this embodiment, each RF network node 104 mayuse the new random number seed 730 to transmit different information indifferent time slots. This may allow for the storage of different dataacross the more than one type of RF network node 104 thereby providingfor distributed memory storage on the plurality of RF network nodes 104.

Referring now to FIG. 8, an embodiment of a communication protocol forarbitration and synchronization in a multiple RF network node 104sub-system (depicted in more detail in FIG. 2) is shown. As shown inFIG. 8, collisions may occur when more than one RF network node 104attempts to transmit a synchronization signal 724 at the same time. Whenthe synchronization signal 724 is transmitted by more than one RFnetwork node 104, all the other RF network nodes 104 may stoptransmitting and wait for the complete signal 734.

A protocol may be advantageous to determine if the RF network nodes 104that may transmit at the same time need to retransmit the random numberfor the determination of a master RF network node 104 (i.e. collisionmanagement). As part of the protocol, there may be a check sequence toverify that the transmitted random number seed 730 is not corrupt; therandom number seed 730 may become corrupt if different random numberswere transmitted.

FIG. 8 shows an example of determination of a master RF network node 104transmission when a collision has occurred and the protocol to correctthe collision. In an embodiment illustrated by the sequences in FIG. 8,two or more RF network nodes 800 and 824 of the N RF network nodes 852may signal the start of the synchronization cycle to indicate a masterRF network node request. Any of the RF network nodes that have notattempted to transmit a synchronization signal may not transmit asynchronization signal and may wait for a complete signal from the finaldetermined master RF network node 104.

As shown in FIG. 8, if a first RF network node 800 and a second RFnetwork node 824 transmit a synchronization signal 802 and 828 andrandom number seed 808 and 832 at the same time, there may be atransmission collision. As depicted in this figure, other RF networknodes 852 that have not yet transmitted a synchronization signal 854would then not transmit a synchronization signal 854, wait signals 858and 862, random number seed 860, and complete signal 864 (all shown bydashed lines) until a complete signal has been transmitted to theantenna bus. In an embodiment, a complete signal may not be transmitteduntil all transmission collisions are resolved.

As depicted in FIG. 8, if there is a collision of the transmission fromthe first RF network node 800 and the second RF network node 824, thecombined random number seeds 808 and 832 from the first RF network node800 and the second RF network node 824 may collide on the antenna bus868 and may become corrupt. In an embodiment, there may be a checksequence in each RF network node that transmits a random number seed toverify that the random number seed 874 on the antenna bus 868 matchesthe transmitted random number seed 808 and 832. In an embodiment, eachRF network node that transmits a random number seed 808 and 832 maystore the random number seed 808 and 832 in a storage location forcomparison to the transmitted random number seed 808 and 832. In anembodiment, if the random number seeds 808 and 832 are transmitted atthe same or different times, the resulting antenna bus 868 random numberseed 874 may become corrupted and may not match the transmitted randomnumber seeds 808 and 823.

As depicted in FIG. 8, if the antenna bus 868 random number seed 874does not match the transmitted random number seed 808 and 832 the firstRF network node 800 may not transmit the complete signal 812 and thesecond RF network node 824 may not transmit the complete signal 834(both shown as dashed lines). In this case, the non-matching randomnumber seeds may be an indication that there was a collision between atleast two RF network nodes attempting to be the master RF network node.

In an embodiment, after the collision of the random number seeds, thefirst RF network node 800 and the second RF network node 824 may attemptto retransmit a second synchronization signal 814 and 840 and a secondrandom number seed 818 and 844 at random times to avoid anothertransmission collision. For example, the second RF network node 824 mayuse a random wait time 838 before attempting to retransmit its secondsynchronization signal 840.

In the example of FIG. 8, the first RF network node 800 is shownre-transmitting the synchronization signal 814 before the second RFnetwork node 824 synchronization signal 840. In an embodiment, this maycause the second RF network node 824 to not transmit the synchronizationsignal 840, random number seed 844, and complete signal 850 (all shownby dashed lines) because the first RF network node 800 transmitted thesynchronization signal 814 first. The first RF network node 800 may thencompare the transmitted random number seed 818 with the random numberseed 882 on the antenna bus 868. If they are the same number, the firstRF network node 800 may transmit the complete signal 822. In anembodiment, the transmission of a complete signal 822 to the antenna bus868 may indicate to the other RF network nodes that a master has beendetermined and to use the random number seed 882 on the antenna bus 868for control of any RF network node functions. In an embodiment, each ofthe other RF network nodes may receive and store each random number seedtransmitted to the antenna bus. Once the other RF network nodes receivea complete signal 822, the other RF network nodes may retain the lastreceived random number seed as the master RF network node random numberseed.

In an embodiment, this sequence of transmitting a synchronization signaland random number seed, checking the transmitted random number seed forcorruption, and re-transmitting as necessary may be repeated until thetransmitted random number seed on the antenna bus 868 is not corrupted.The random number seed may be considered not corrupt if the antenna bus868 random number seed 882 matches the transmitted random number seed818. In an embodiment, a non-corrupted antenna bus 868 random numberseed may indicate that a master RF network node has been selected.

In an embodiment, more than one master RF network node may be selectedif more than one RF network node transmits the same random number seedat the same time. In an embodiment, the selection of more than one RFnetwork node as a master RF network node may indicate that more than oneRF network node transmitted the same random number seed at asynchronized time.

As a result of the above-described transmission by the first RF networknode 800 and the second RF network node 824, the antenna bus 868received signal may be as shown in FIG. 8. In an embodiment, the antennabus 868 may receive a combined synchronization signal 870, wait time872, and a combined random number seed 874 from the first RF networknode 800 and the second RF network node 824. The random number seed 874may have been a corrupt signal because of the random number seed 808 and832 being transmitted at the same time. There may then be a randomlength wait time 878 while the first 800 and second 824 RF network nodeswait random times to retransmit their signals. In an embodiment, theantenna bus 868 may then receive the synchronization signal 880, randomnumber seed 882, and complete signal 884 from the first RF network nodeto retransmit. As depicted in FIG. 8, the first RF network node 800 maytransmit first.

In an embodiment, receiving the complete signal 884 on the antenna bus868 may be an indication to the other RF network nodes that a master RFnetwork node has been determined and the random number seed 882 on theantenna bus is to be used for any RF network node functions. In anembodiment, the determined master RF network node(s) may continue tooperate as the master RF network node of the RFID tag for the length ofthe RFID tag 102 read. In an embodiment, a different RF network node maybe selected as the master RF network node with the next power upsequence.

In another embodiment of a master RF network node 104 determination, allthe RF network nodes 104 may operate as peers, and a discovery protocolmay be used to assign a role to each of the nodes. The role assignmentmay provide a distinct number assignment to each RF network node 104,which may be used by the RF network node 104 to understand its role inbecoming a master RF network node or a slave RF network node. In anembodiment, each RF network node 104 may include a table that may definethe role of each RF network node 104 on the RFID tag 102. In anembodiment, the table may be the same for each RF network node 104,different for each RF network node 104, or the like. For example, theRFID tag 102 may include four RF network nodes. The table included witheach RF network node may indicate that node two is to become the masterRF network node and the other three RF network nodes 104 are to becomeslave RF network nodes. During power up, RF network node 104 two maybecome the master network node of the RFID tag 102. In an embodiment,the table may also include information of which RF network node 104 maybe redundant to one of the other RF network nodes 104 in the situationwhere the RF network node 104 was to stop functioning.

Using one of the above described master RF network node determinationprotocols, it may be determined which RFID tag 102 RF network node is amaster RF network node and which are the slave RF network nodes. Indetermining the master RF network node, the functions of the multiple RFnetwork nodes 104 on an RFID tag 102 may be coordinated by a single RFnetwork node 104 to provide increased functionality such as distributedmemory, RF network node redundancy, multiple communication frequencies,multiple antenna interfacing, and the like. As previously described, anyof the more than one RF network nodes 104 on the RFID tag 102 may becomethe master RF network node.

In an embodiment, the master RF network node may provide the interfacefunction between the RFID tag 102 and the reader 140, inter RF networknode 104 communication, memory management, redundant RF network node 104protocol, or the like, as depicted in FIGS. 1 and 2. In an embodiment,with one RF network node 104 coordinating the functionality of the RFIDtag 102, the multiple RF network node RFID tag 102 may appear as asingle chip RFID tag to a standard RFID reader 140. The master RFnetwork node may provide management of the RFID tag 102 functionalitythat may include coordination of all the RF network node 104 memoriesthat may provide for increased amounts of accessible memory for a singleRFID tag 102. In embodiments, coordination may be according to a networktopology among RF network nodes, and may be associated with theinter-node interface 154, common antenna connection 158, communicationsfacility 134, and the like. In embodiments, coordination may be throughtag-to-tag communications 3008 as described herein. The network topologymay be a ring network topology, a mesh network topology, a serialtopology, a packet-based network topology, or the like, where ‘topology’may refer to the configuration of a communication. In embodiments, theserial topology may utilize serial bus technologies and configurationsdescribed herein. As will be described below, the accessible memory maybe accessed as combined memory, increased memory, a combination ofcombined and increased memory for redundancy, private memory, publicmemory, user memory, and the like.

In an embodiment, the slave RF network nodes (any of the non-master RFnetwork nodes 104) may receive commands from the master RF network nodeto be executed. In an embodiment, as a slave, RF network node 104 mayperform any function, command, memory request, or the like that may betransmitted from the master RF network node. In an embodiment, the slaveRF network nodes may become specialized in functions that are performed.For example, the individual slave may provide the encryption, passwordprotection, communication interface control, or the like for the masterRF network node. Additionally, the slave RF network node may providecertain amounts of memory, types of memory (e.g. private, public),redundant memory, or the like that may be coordinated by the master RFnetwork node.

In an embodiment, the RF network node 104 redundancy may be executed byeither the master RF network node or slave network node. For example, ifa slave RF network node was to become damaged and stop functioning, themaster RF network node may determine the protocol for at least one otherRF network node 104 providing redundant functionality, memory, or thelike for the damaged slave. In another example, if the master RF networknode was to become damaged and stop functioning, the slave RF networknodes may follow a protocol in determining which slave RF network nodewill become the master RF network node.

In an embodiment, referring to FIGS. 1 and 2, the RFID tag 102 maycommunicate with the RFID reader 140 using a single RF network node 104,using a single master RF network node 104, using a plurality of RFnetwork nodes 104, or the like. Using the single transmitting RF networknode 104, the single RF network node 104 may coordinate the informationrequested by the reader 140 from the other RF network nodes 104 that maybe on the RFID tag 102. In an embodiment, the single RF network node 104may receive the reader 140 request and, depending on the request, thesingle RF network node 104 may request information from the other RFnetwork nodes 104 on the RFID tag. After all the information has beenreceived from the other RF network nodes 104, the single RF network node104 may transmit the requested information back to the reader 140.

Using a plurality of transmitting RF network nodes 104, some or all ofthe plurality of RF network nodes 104 may transmit the requested reader140 information all at the same time, at different times, or the like.In one embodiment, the plurality of RF network nodes may transmit inordered time slots to transmit individual parts of the total requestedinformation in an ordered sequence back to the reader 140. In anotherembodiment, all the RF network nodes 104 may simultaneously transmitinformation to the reader 140. In an embodiment, the simultaneoustransmission and ordered time slot transmission from the plurality of RFnetwork nodes 104 may require a synchronizing of the plurality of RFnetwork nodes 104.

In one embodiment, after the multiple RF network nodes 104 have beenapplied to the RFID tag 102, information related to the transmissionprotocol (e.g. as single or multiple RF network nodes) may be programmedinto the RF network nodes 104. As shown in FIG. 9, the transmissionprotocol information may be programmed 914 to the RF network nodes 104.In an embodiment, the programming 914 may be the storing of thetransmission protocol into the RF network node 104 non-volatile memoryto be recalled during a read of the RFID tag 102. In an embodiment, theprogramming 914 may be performed by a reader 140 type device that isable to communicate with the RF network nodes and store the transmissionprotocol information within the RF network node 104 memory. In anotherembodiment, the transmission protocol may be part of the firmware orhardware of the RF network nodes 104 as part of the RF network node 104manufacture. Therefore, the transmission protocol of the RFID tag 102may be determined when the RF network nodes 104 are assembled to theRFID tag 102.

Referring to FIG. 9, an embodiment of the RFID tag 102 communicatingwith the reader 140 is shown. In embodiments, the reader 140 maycommunicate with the RFID tag 102 in different protocols, based onwhether the RFID tag 102 is communicating with a single RF network node104 or a plurality of RF network nodes 104. In an embodiment ofcommunicating with a plurality of RF network nodes 104, the RFID tag 102may communicate with the reader 140. The reader 140 may be a stand-alonedevice or may include a synchronicity device 918, an interrogator device920, a reader device 922, or the like. In an embodiment, the process ofreading the plurality of RF network nodes 104 may include sending asynchronicity signal and an interrogator signal, and the RFID tag 102may respond by reflecting or broadcasting an RF signal containing theinformation stored in the RFID tag 102 memory.

In an embodiment, the synchronicity device 918 may send an RF signalthat may initialize and synchronize the internal clocks of a pluralityof RF network nodes 104. In certain embodiments, the RF network node 104may not have a physical internal clock. In these embodiments, receipt ofthe synchronicity signal by the plurality of RF network nodes 104 mayinitiate a process within the plurality of RF network nodes 104 that mayresult in synchronization. In a situation where there are multiple RFnetwork nodes 104 associated with an antenna 108, the plurality of RFnetwork nodes 104 may receive the synchronicity signal and thesynchronicity signal may initiate a substantially identical processwithin each RF network node 104. This may result in a substantiallyidentical transmission of data from the multiple RF network nodes 104,for example. This step may allow all of the RF network nodes 104 toreflect or broadcast an RF signal at the same time and therefore reflector broadcast as if there were one RF network node. As another example,the synchronicity may allow the plurality of RF network nodes 104 totransmit information in a timed sequence from each of the plurality ofRF network nodes 104; in this manner, the reader 140 may receiveinformation as if a single RF network node 104 transmitted it. In anembodiment, the synchronicity device 918 may be included in the RFnetwork node 104. When the RF network node 104 is energized, a signalmay be received from the interrogator device 920 or the reader device922 to calibrate the RF network node 104, the calibration may initiatethe logic and internal clock synchronization. In another embodiment,when the RF network node 104 is energized, the RF network node 104 mayinitiate a calibration sequence to initialize all the nodes in the RFIDtag 102. This may include RF network node functionality configuration,clock frequencies, and the like.

In an embodiment, the interrogator device 920 may send an RF signal thatmay request the RFID tag 102 to reflect or broadcast its informationstored in memory. For a passive RFID tag, the interrogator device 920 RFsignal may also energize the RFID tag 102. In an embodiment, theinterrogator device 920 may include the synchronicity device 918 andtherefore may initialize the plurality of RF network nodes 104 andrequest information to be reflected or broadcast.

In an embodiment, the reader device 912 may receive reflected orbroadcast information from the RFID tag 102. This information may relateto the item with which the RFID tag 102 is associated. The reader device922 may listen for a certain frequency to be reflected or broadcast ormay listen for a plurality of frequencies. The reader device 922 may beconnected to a computer device (e.g. computer, server, or network) foraggregation of the received information.

In an embodiment involving communicating with a single master RF networknode, the RFID tag 102 may communicate with the reader 140. The reader140 may be a stand-alone device or may include the interrogator device920, the reader device 922, or the like; the synchronicity device 918may not be required when communicating to a master RF network node 104.As previous described with master RF network nodes, upon power-up, theslave RF network nodes may respond to the command request from themaster RF network node.

In an embodiment, when communicating with a RFID tag 102 using a masterRF network node 104, the interrogator device 920 may transmit aninformation request to the RFID tag 102. The plurality of RF networknodes 104 may power-up and determine which RF network node will becomethe master RF network node. Once the master RF network node has beendetermined, the master RF network node will receive the informationrequest from the interrogator 920. In an embodiment, the master RFnetwork node may coordinate any information that may be provided by theother RF network nodes on the RFID tag 102.

In an embodiment, once the master RF network node has receivedinformation required from the other RF network nodes 104, the master RFnetwork node may transmit the requested information. Within the reader140, the reader device 922 may receive the information. Once theinformation is received, it may be communicated to a connected computer,server, network, or the like.

As previously described, the RFID antenna 108 may provide the reflectingor broadcasting means for the RFID tag 102 by reflecting or broadcastingthe signal generated by the RF network nodes 104 that may be connectedto the antenna leads. The antenna 108 may be configured in variousshapes such as a bar, loop, patch, or the like. The antenna leads may beused to connect the antenna 108 to the RF network nodes 104. The antennaleads may be in a configuration that may have the leads of a first halfof the antenna in close proximity to a second antenna lead. The twoantenna leads may be close enough to allow the leads on the RF networknode 104 to make contact between the first antenna lead and the secondantenna lead. The configuration of the two antenna leads may be of anyshape as long as the space between the two leads may be bridged by theRF network node 104. The RF network node 104 may contain at least twoexternal leads that may be connected to the antenna leads. The RFnetwork node 104 leads may be configured on the RF network node 104advantageously for bridging the space between the two antenna leads, forexample on different sides of the RF network node 104.

The RF network node 104 may provide an information radio frequencysignal, using the antenna 102, in response to an interrogator's 120request. Upon the request from the interrogator 120, the RF network node104 may reflect or broadcast information stored in the memory. Theinformation previously may have been stored in the memory; theinformation may relate to the item to which the RFID tag 102 isattached. The RF network node 104 may reflect or broadcast at a setfrequency that may be received by a particular reader 922 type.

Referring to FIG. 10, an embodiment of a schematic of four RF networknodes (104A, 104B, 104C, 104D) associated with an antenna 108 is shown.An aspect of the systems and methods described herein may involve morethan one RF network node (104A, 104B, 104C, 104D) communicating andfunctioning as a single RFID tag 102. In an embodiment, redundancy maybe achieved by at least one RF network node (104A, 104B, 104C, 104D)providing a backup to another RF network node (104A, 104B, 104C, 104D)that may have become damaged or has otherwise lost functionality. Thebackup may be either functional, where the backup RF network nodeprovides the function of the damaged RF network node, or memory, wherethe RF network node provides a backup for the memory of the damaged RFnetwork node (104A, 104B, 104C, 104D). For example, if RF network node104A were to become damaged, one or more of the other RF network nodes(104B, 104C, 104D) may assume the function or memory of the damaged RFnetwork node 104A. In an embodiment, there may be more than one methodof determining which of the other RF network nodes (104B, 104C, 104D)will assume the function of the damaged RF network node 104A.

In an embodiment, the simplest method of redundancy may involve all ofthe RF network nodes (104A, 104B, 104C, 104D) having the same functionand memory, so that, the RFID tag 102 will continue to function as longas one RF network node (104A, 104B, 104C, 104D) continues to function.In another embodiment, there may be RF network nodes (104A, 104B, 104C,104D) that have different functions within the RFID tag 102. Thedifferent functions may include encryption, sensor reading, privatememory, public memory, or the like. In an embodiment, the RF networknodes (104A, 104B, 104C, 104D), while having different functions, mayhave a common core of logic to allow one RF network node (104A, 104B,104C, 104D) to perform the requirements of another RF network node(104A, 104B, 104C, 104D). In an embodiment, all of the RF network nodes(104A, 104B, 104C, 104D) may be identical, but during power up, thedifferent RF network nodes may assume different roles on the RFID tag102.

In the case of an RF network node (104A) being damaged, one of the otherRF network nodes (104B, 104C, 104D) may be able to assume the role ofthe damaged RF network node (104A). In an embodiment, when an RF networknode (104A) is damaged and another RF network node (104B, 104C, 104D)assumes the function of the damaged RF network node (104A), there may bea loss of some functionality of the RFID tag 102. In an embodiment, thefunction of the damaged RF network node (104A) may be assumed by morethan one of the other RF network nodes (104B, 104C, 104D) to provide allthe functionality of the damaged RF network node (104A). It should beunderstood by someone knowledgeable in the art that there may be manydifferent configuration methods of one RF network node (104A, 104B,104C, 104D) providing redundancy to another RF network node (104A, 104B,104C, 104D).

In another embodiment, there may be a pre-assignment as to which RFnetwork node (104A, 104B, 104C, 104D) becomes the redundant RF networknode (104A, 104B, 104C, 104D) for another RF network node (104A, 104B,104C, 104D). In an embodiment, the assignment of redundancy may be inthe firmware of the RF network nodes (104A, 104B, 104C, 104D), in thedata of the RF network nodes (104A, 104B, 104C, 104D), or the like. Inthis configuration, if an RF network node (104A, 104B, 104C, 104D) isdamaged, there may be a pre-assigned replacement for the non-functioningRF network node (104A, 104B, 104C, 104D). For example, if one RF networknode 104A is damaged it may be predetermined that a second RF networknode 104B will provide the redundant function for the damaged RF networknode 104A. It should be understood that there may be a series ofpre-assigned redundancy for damaged RF network nodes (104A, 104B, 104C,104D). The pre-assignment may provide for a single RF network node(104A, 104B, 104C, 104D) redundancy, a combination of RF network node(104A, 104B, 104C, 104D) redundancies, or the like. It should beunderstood that there may be a number of pre-assigned redundancyconfigurations that would be consistent with the systems and methodsdescribed herein.

In another embodiment, a communication protocol may determine which RFnetwork node (104A, 104B, 104C, 104D) is to be the redundant RF networknode (104A, 104B, 104C, 104D). In an embodiment, similar to the masterRF network node communication described in FIG. 7 and FIG. 8, theremaining functional RF network nodes (104A, 104B, 104C, 104D) capableof being a redundant RF network node (104A, 104B, 104C, 104D) maytransmit a signal to indicate that any one of them is available toreplace the damaged RF network node (104A, 104B, 104C, 104D). In anembodiment, more than one RF network node (104A, 104B, 104C, 104D) maysignal to become the redundant RF network node (104A, 104B, 104C, 104D)and a protocol of collision resolution may be used to determine whichwill be the redundant RF network node (104A, 104B, 104C, 104D). Forexample, two RF network nodes 104A and 104B may each attempt to signalto be the redundant RF network node. Following the signal protocol, eachRF network node 104A and 104B may determine a time slot to send theredundant signal; the first to transmit the signal may become theredundant RF network node. In the case of both RF network nodes 104A and104B signaling at the same time, a protocol may be employed to resolvethe collision and retransmit the signal to determine which one becomesthe redundant RF network node. In an embodiment, the resolution protocolmay continue until it is determined which one of the RF network nodes104A or 104B will become the redundant RF network node.

In an embodiment, the RFID tag 102 may be able to report the status ofthe RF network nodes (104A, 104B, 104C, 104D) in the RFID tag 102. Thismay allow for advance notice of a potential permanent disablement of theRFID tag 102, which can then provide the basis for appropriate remedialactions. For example, the RFID tag 102 may contain four RF network nodes(104A, 104B, 104C, 104D) but two may have become damaged and theremaining two RF network nodes are providing redundant functionality ormemory. In this example, the damaged RF network nodes may reduce theover all functionality of the RFID tag 102. The RFID tag may communicatein a transmission to the reader 140 that there are damaged RF networknodes and that the RFID tag 102 functionality has been reduced. This mayprovide notice to replace the RFID tag to restore full functionality andinformation recording.

In a similar manner to the functional redundancy, the RF network node(104A, 104B, 104C, 104D) memory may also have a redundancy protocol. Inan embodiment, the plurality of RF network nodes (104A, 104B, 104C,104D) may create a distributed memory to be used in configurations suchas redundant memory or increased memory to the RFID tag 102. Theredundant memory configuration may have each of the more than one RFnetwork nodes (104A, 104B, 104C, 104D) storing the same information,thereby providing a memory configuration that may maintain the RFID tag102 information as long as one of the RF network nodes (104A, 104B,104C, 104D) is operational. The increased memory configuration mayaccess the individual RF network node (104A, 104B, 104C, 104D) memory asa single memory to store increased amounts of memory for the RFID tag102. In an embodiment, either of these memory configurations may supportpublic memory, private memory, encrypted memory, read once/write many,read/write, read only, or the like.

In an embodiment, each of the more than one RF network nodes (104A,104B, 104C, 104D) may store the same memory information in the redundantmemory configuration, so that on the same RFID tag 102, the sameinformation may be stored on each of the individual RF network nodes(104A, 104B, 104C, 104D). In this redundant memory configuration, theRFID tag 102 information may be maintained as long as one of the RFnetwork nodes (104A, 104B, 104C, 104D) continues to operate. In anembodiment, the redundant memory configuration may be used on componentsthat operate in environmentally challenging locations such as hightemperatures, high stress, or the like where there may be a possibilityof the RFID tag 102 being damaged.

In an embodiment, the distributed memory may provide for increasedmemory where the memory of the more than one RF network nodes (104A,104B, 104C, 104D) function as a combined single memory store, so thatthe memory may be the sum of all the RF network node (104A, 104B, 104C,104D) memory. For example, if each of the RF network nodes (104A, 104B,104C, 104D) have 8K of memory, the total memory of a four RF networknode RFID tag 102 would be 32K of memory. In an embodiment, theincreased memory RFID tag 102 may be used on components that are in aless stressful environment, where the RFID tag 102 is less likely to bedamaged.

In another embodiment, the distributed memory may store a combination ofdata and metadata. In an embodiment, the RFID tag 102 may store dataonly until a reader reads the data. As part of the data read, the RFIDtag 102 data may be cleared and metadata indicating an external networkstorage location of the data just read from the RFID tag 102 may bewritten to the RFID tag 102. In this manner, the RFID tag 102 may beable to record and store more data than would otherwise be possible withthe limited amount of memory on the RFID tag 102. Over time, datarecorded by the RFID tag 102 may be stored on an external data storewith only metadata stored on the RFID tag 102.

An additional advantage to this memory configuration may be that datawould not be lost if the RFID tag 102 were damaged and stoppedfunctioning. In an embodiment, if the RFID tag 102 is damaged, it may bereplaced with a new RFID tag 102 and the existing metadata loaded to thenew RFID tag 102, thereby providing for continued data recording fromthe same component without a loss of data by means of the new RFID tag102.

In an embodiment, the different memory configurations may be usedindividually or in combination to provide the memory configurationrequired for the RFID tag 102 type. For example, in a four RF networknode (104A, 104B, 104C, 104D) RFID tag 102, two RF network nodes (104A,104B) storing the same information may create redundant memory; this maybe repeated for the other two RF network nodes (104C, 104D), with afinal result of two sets of redundant RF network nodes (104A, 104B) and(104C, 104D). Additionally, the two sets of RF network nodes (104A,104B) and (104C, 104D) may then be combined as increased memory for theRFID tag 102. This configuration may result in two sets of redundantincreased memory for the RFID tag 102. It may be understood by oneknowledgeable in the art that the RF network nodes (104A, 104B, 104C,104D) may use in a number of different redundant and increased memoryconfigurations.

In an embodiment, the RF network node memory configuration may be set inthe hardware, firmware, software configured, or the like. In anembodiment, the memory configuration may be programmed into the RFID tag102 when it is associated with a component.

In an embodiment, in either a redundant or increased memoryconfiguration, the master RF network node may manage the memory of theRFID tag 102. As part of the hardware, firmware, software, or likeconfigurations of the RFID tag 102, different parts of the RFID tag 102memory may be assigned different read/write permissions. For example,there may be private memory, public memory, user memory, read onlymemory, write once/read many memory, read/write, and the like that maybe used for different information dependent on the different entitiesthat needed access to the information. In an embodiment, the master RFnetwork node may manage the different memories, memory configurations,memory read types, and the like within the RFID tag 102. In anembodiment, the may be predetermined memory locations and memoryallocations for the different types of memory within the RFID tag 102.

In an embodiment, public memory may be used for information that can beread may any entity or enterprise that is able to read the informationfrom the RFID tag 102. For example, any enterprise along a distributionroute for a product with an RFID tag 102 may be able to read the nameand quantity information of the product. But only certain enterprisesmay be able to read the distribution history of the product, the ownerinformation, serial number information, final delivery information, orthe like. This information may be in private memory and may beencrypted, protected with a password, or the like.

In an embodiment, the RFID tag 102 may have user specific memory thatonly the owner of the product may access. The user memory may bestructured or non-structured memory that may allow the user to write anyinformation to these locations. The user memory may be encrypted,password protected, or the like.

In an embodiment, public, private, or user memory may be read only,write once/read many, read/write, or the like. In an embodiment,information in the read only memory may be written to the RFID tag 102when the RFID tag 102 is initially associated with the object. This maybe information that the owner of the object does not want to havereplaced or lost during the life span of the object such as the objectname, the object quantity, the object serial number, or the like.

In an embodiment, information in the write once/read many memory may beinformation that is added to the RFID tag 102 during the life span ofthe object. This may be information that the owner of the object doesnot want to have replaced or lost during the life span of the object.For example, the object may be in a distribution system. At each stop,change of transportation system, change of carrier, or the like thatoccurs during the distribution of the object, information may be writtento the RFID tag 102 to provide a distribution history of the object. Theowner of the object may want the distribution information written to theRFID tag 102 but may not want to have the information overwritten orerased because this information may provide a distribution history ofthe object. But, once the information is written to the RFID tag 102,the owner of the object may want to read the distribution informationmany times. In an embodiment, the write once\read many memory may bepublic, private, or user memory.

In an embodiment, information in the read/write memory may beinformation that is temporary information to the RFID tag 102 during thelife span of the object. The read/write memory may be overwritten duringthe life span of the object and may be used to provide temporaryinformation, information of the last state of the object, informationcontaining the changing state of the object (e.g. changing weight), orthe like. For example, the RFID tag 102 may be on a pallet that holds anumber of identical objects. Every time an object is removed from thepallet, the number of objects remaining on the pallet may be revised inthe read/write memory of the RFID tag 102. In this example, theread/write memory may be public, private, or user memory.

As previously described herein, the RFID tag 102 may include acommunication facility 134 that may provide communication to externalfacilities 138, such as devices, networks, interfaces, or the like thatare external to the RFID tag 102. Referring to FIG. 11, an embodiment isshown of the RFID tag 102 communicating with a plurality of sensors(138AA, 138AB, 138AC), a gateway facility 138C, and a cellular network138EA. In an embodiment, the communication facility 134 may be connectedto more than one external facility 138 at the same time. For example,the communication facility 134 may be connected to a self-powered sensor138AA and a gateway facility 138C. This may allow the RFID tag 102 toread the self-powered sensor 1102 and communicate the reading to anetwork that may be connected to the gateway facility 138C.

In an embodiment the gateway facility 138C may provide communication toan external network that may include a LAN, a WAN, a peer-to-peernetwork, an intranet, an Intranet, or the like. In an embodiment, theconnection between the gateway facility 138C and the communicationfacility 134 may be wired or wireless. The wireless connection mayinclude WiFi, Bluetooth, wireless USB, ultra-wideband, or the like. Inan embodiment, the gateway facility 138C may be able to transmit andreceive information to and from the network. In an embodiment, byconnection to a gateway facility 138C, the RFID tag 102 may beconsidered computer device on a network where information may be inputand output. For example, as information is stored on the RFID tag 102from a reader 140 or sensor (138AA, 138AB, 138AC), the storedinformation may be transmitted to the network using the communicationfacility 134 connected to the gateway facility 138C. Additionally,information may be stored on the RFID tag 102 from the network. Forexample, during a read cycle, the RFID tag 102 may check the connectedgateway facility for any information that may be waiting to betransferred from the network.

In another embodiment, RFID tags 102 may be able to communicate witheach other using the connected gateway facility 138C. In thisembodiment, a group of RFID tags 102 may form an RFID tag 102 networkwhere information may be communicated between the each other using thegateway facility 138C network connection. For example, in addition orinstead of communicating information to the reader 140, when the RFIDtag 102 is powered up by a reader 140 signal, the RFID tag 102 maycommunicate information to other RFID tags 102 using the gatewayfacility 138C. There may be more than one RFID tag 102 within an areathat also have gateway facility 138C connections that may receive andtransmit information to and from other RFID tags 102. The RFID tags 102may be able to communicate any information stored within the RFID tag102 memory using the gateway facility 138C. The inter RFID tag 102communication may provide a method of data backup among the RFID tags102, may provide an RFID tag 102 distributed memory, may provide an RFIDtag 102 shared memory, or the like.

In an embodiment, the cellular network 138EA connection may provideanother method of communicating information to a network. In certainsituations, the RFID tag 102 may not be directly connected to a gatewayfacility 138C network but may have connectivity through the cellularnetwork 138EA. The cellular network 138EA may provide the RFID tag 102access to a cellular network provider and thereby access to a networkfor communicating the RFID tag 102 information. Similar to the gatewayfacility 138C connection, the RFID tag 102 may be able to transmitinformation to and from the cellular network 138EA as information iswritten to the RFID tag 102.

In an embodiment, the gateway facility 138C and cellular network 138EAconnections may provide traceability of the RFID tag 102 throughout itslife cycle. For example, as a product moves through a distributionsystem it may have a plurality of read cycles that may write informationto the RFID tag 102. As the RFID tag 102 receives information, the RFIDtag 102 may be able to communicate the new information through thegateway facility 138C or cellular network 138EA. In this manner, theinformation on the RFID tag 102 may be recorded and tracked from aremote location connected to the network. For example, the owner of theRFID tag 102 product may be able to track the progress of the productthrough the distribution system from the remotely connected location.

In an embodiment, the RFID tag 102 communication facility 134 may beconnected to both the gateway facility 138C and the cellular network138EA. Depending on the location of the RFID tag 102 when newinformation is written, the RFID tag 102 may select either the gatewayfacility 138C or cellular network 138EA to communicate the newinformation to the network. For example, in a more remote location, thecellular network 138EA may provide the network connection when thegateway facility may not have connectivity to a network.

In an embodiment, the RFID tag 102 may be able to connect to the networkthrough the gateway facility 138C or cellular network 138EA during powerup, at full power, or the like. In embodiments, the RFID tag 102 may bepowered up by ambient electro-magnetic waves, by a reader signal, by anelectro-magnet signal device, or the like. For example, the RFID tag 102may power up every time there is an ambient electro-magnetic wave thatis strong enough to provide power to the RFID tag 102. During any of theambient wave power ups, the RFID tag 102 may attempt to communicate withthe network using the gateway facility 138C or cellular network 138EA.In another example, there may be a device that periodically generates asignal that may power up the RFID tag 102 to communicate with thenetwork.

In an embodiment, the sensors (138AA, 138AB, 138AC) may provideinformation such as temperature, humidity, stress, acceleration, or thelike to the RFID tag 102. In an embodiment, the sensors (138AA, 138AB,138AC) may be self-powered 138AA, RFID tag powered 138AB, require nopower 138AC, or the like.

In an embodiment, the communication facility 134 may provideconnectivity between the RFID tag 102 and the sensors (138AA, 138AB,138AC). In embodiments, the communication facility 134 may be a directinterface, a serial interface, a parallel interface, a gatewayinterface, a network interface, or the like. In an embodiment, any ofthe interface types may be implemented as a wired or wirelessconnection. In an embodiment, the wireless connections may be a cellularconnection, a WiFi connection, an infrared connection, a Bluetoothconnection, wireless USB, ultra wideband, or the like. In an embodiment,the communication facility 134 may provide a connection to the sensors,a network, other RFID tags, or the like.

In an embodiment, the RFID tag 102 using a wireless communicationinterface 134, may be located remotely from the sensors (138AA, 138AB,138AC). This may allow the RFID tag 102 to be in a location that may beless susceptible to damage and still collect data from a sensor (138AA,138AB, 138AC) that may be in an environment that would be damaging tothe RFID tag 102.

Additionally, using the communication facility 134, the RFID tag 102 maybe able to communication with more than one sensor (138AA, 138AB, 138AC)using either a wired or wireless connection. In this embodiment, theRFID tag 102 may network a number of sensors together to collect andsave the sensor information.

In an embodiment, the communication facility 134 may be a separatedevice from the RFID tag 102, part of the RFID tag 102, a combination ofseparate and part of the RFID tag 102, or the like.

In an embodiment, the RFID tag 102 may read the sensors (138AA, 138AB,138AC) during power up, at full power, or the like. In embodiments, theRFID tag 102 may be powered up by ambient electro-magnetic waves, by areader signal, by a electro-magnet signal device, or the like. Forexample, the RFID tag 102 may power up every time there is an ambientelectro-magnetic wave that is strong enough to provide power to the RFIDtag 102. During any of the ambient wave power ups, the RFID tag 102 mayread the data from the sensors (138AA, 138AB, 138AC). In anotherexample, there may be a device that periodically generates a signal thatmay power up the RFID tag 102 to read the sensors (138AA, 138AB, 138AC).In another example, the sensors (138AA, 138AB, 138AC) may contain memoryfor the sensor readings taken during a read using ambient waves and theRFID tag 102 may read the sensor stored data when the RFID tag 102receives a reader 140 signal.

In an embodiment, the self-powered sensor 138AA may be powered by anexternal source such as AC power, DC power, battery power, or the like.Because of the constant power source, the self-powered sensor 138AA maycontinuously measure and provide data to the RFID tag 102. The RFID tag102 may only read the continuously provided data when the RFID tag 102is powered up.

In an embodiment, the RFID powered sensor 138AB may be powered only fromthe RFID tag 102. In an embodiment, when the RFID 102 is powered up, theRFID tag 102 may provide power to the RFID powered sensor 138AB. Forexample, the RFID tag 102 may power up from a received signal, the RFIDtag 102 may send power to the RFID powered sensor 138AB, the RFIDpowered sensor 138AB may read data, and the RFID tag 1102 may then readand store the RFID powered sensor 138AB data.

In an embodiment, the no power sensor 138AC may not require any power toread data, and may instead wait for the RFID tag 102 to request data.For example, the RFID tag 102 may power up from a received signal, theRFID tag 102 may request data from the no power sensor 138AC, the nopower sensor 138AC may read data, and the RFID tag 102 may then read andstore the no power sensor 110 data.

It may be understood by someone knowledgeable in the art that there maybe a number of different types of sensors (138AA, 138AB, 138AC) usedindividually or in combination with at least RFID tag 102.

In embodiments, there may be a number of methods of assembling the RFnetwork nodes 104 as described herein to the RFID tag 102. The RFnetwork nodes may be applied by mechanical direct placement, conductiveink transfer, thermal ink transfer, silkscreen, or the like. In anembodiment, non-precise RF network node 104 placement processes such asconductive ink transfer, thermal ink transfer, silkscreen, or the likemay be applied to an area of the RFID tag 102 where there are antennaleads that are closely spaced. As depicted in FIG. 9, the antenna 108may have connection leads; these leads may be of various designs thatmay provide for small gaps between the two antenna 108 halves. The smallgap between the antenna 108 leads may allow the RF network node 104leads to bridge the gap and make contact to both halves of the antenna108. The two antenna 108 leads may branch into a plurality of leads; theplurality of leads of the two antennas 108 may be in close proximity ina certain area on the RFID tag 102. This certain area may be where theRF network nodes 104 are applied to the RFID tag 102. In embodiments,the gap between the leads may be small enough to allow the RF networknode 104 to bridge the antenna 102 lead gap.

In embodiments, the mechanical direct placement method may includetraditional chip placement such as flip-chip, direct attach, strapattach, PICA, and the like. Using the mechanical direct placement, theRF network node 104 may be place on a substrate using mechanical means.The mechanical direct placement method may be able to precisely placethe RF network node 104 to the antenna 108 leads.

In embodiments, the RFID tag 102 may be assembled with the use of asuper strap, where the super strap may be a substrate, carrier,interposer, and the like, with the function of packaging a system ofintegrated circuits (IC) chips. By providing a physical place holder formultiple IC chips, such as RFID nodes 104, RFID chips, sensors, memoryand the like, several chips may be interconnected. Theseinterconnections may be a network of series, parallel, series-parallel,and the like, between IC chips located on a super strap. For instance,FIG. 9AA shows a representation of how multiple ICs may be connected ina series configuration, FIG. 9AB how multiple ICs may be connected in aparallel configuration, and FIG. 9AC how multiple ICs may be connectedin a series-parallel configuration. These three representativeconfigurations are meant to illustrate the possible interconnections,and not to be limiting in any way. One skilled in the art will recognizethat there are a wide variety of configurations for interconnectingmultiple ICs. In embodiments, a super strap may provide convenienceduring manufacturing. In addition, it may provide design advantages forelectrical and RF performance for a multi-node or composite type RFIDtag. In embodiments, a use model of the super strap may be similar to atypical strap used in RFID tags.

In manufacturing, a super strap may improve the assembly time of amulti-node tag 102, where it may be manufactured prior to the attachmentof the antenna 108 with a network of multiple chips. Although a superstrap may carry multiple chips, there may be only a limited number ofconnections (e.g. only two connection points for a dipole antenna).Therefore, a typical high volume manufacturing process may maintain itsproduction throughput by attaching just a single super strap to anantenna 108 at high speed. A super strap may provide improved electricalperformance when connecting multiple ICs. For instance, the closeproximity of the chips on a super strap may deliver the most desiredpositioning of the chips and thus lower electrical losses when sharingdata or power between different IC chips.

In embodiments, the assembly of the RFID tag 102 may be performed byattaching an IC chip, such as RFID node(s) 104, RFID chip(s), to anantenna using a flip-chip assembly process. In some cases, aninterposer, strap, super strap, and the like, may be used in conjunctionwith the assembly process. In practice, an IC chip may only have a smallnumber of external connections, such as two to three externalconnections, implemented as pads, pins, and the like. As RFID chipsincorporate more functionality, as is the case in various embodiments ofthe present invention, one may extrapolate scenarios where theinput/output complexity of the devices creates a need for more externalconnections. For example, the present invention may be implemented in anapplication for driving an external facility 138 such as a display 138Bas described herein, where the input/output demands of the externalfacility 138 may increase with the number of display segments, the sizeof the display, the technology of the display, the functionality of thedisplay, and the like. As the number of external connections increases,a challenge may occur in terms of manufacturing complexity. Forinstance, a chip attach process may dictate minimums on pad spacing andother mechanical limits, translating into a possibility that the IC chip(die) size would need to increase in order to accommodate the assemblyprocess limits. This may have the disadvantage of making the die morecostly. Additionally, this may make the IC chip more vulnerable tomechanical damage in the course of assembly, such as in roll-to-rollprocesses. In embodiments, the present invention may accommodate theincreased input/output demands of an external facility 138 withoutsubstantially increasing the input/output count of the IC chip byutilizing intermediate electronics between the IC chip and externalfacility 138. For example, an IC chip of the present invention mayprovide an RFID device (“IC chip”) where the number of externalinterface signals to one or more external facilities 138 is minimized orreduced by the use of an external multiplexing and/or de-multiplexingarrangement, or other like intermediate electronics, so as to minimizethe size of the chip or to provide other benefit. In embodiments, the ICchip may interface to the intermediate electronics via a serial bus, atime sequenced signal, a phase sequenced signal, and the like. Theintermediate electronics may be implemented using printed electronics,printed in a roll-to-roll process and the like, attached in the sameline as printing the intermediate electronics circuit. In embodiments,the intermediate electronics circuit may be implemented as conventionalsilicon based circuitry, attached in a roll-to-roll process, attached inthe same line as attaching the multiplexing circuit. The intermediateelectronics circuitry may interface to, or be present within, anexternal facility 138, such as a display 138B, a plurality of externalfacilities 138, and the like or any other external facility 138 asdescribed herein. In embodiments, the IC chip may receive and/ortransmit power from or to external facilities 138. In embodiments, thepower signal itself may be used as a communications signal. Inembodiments, the application of the intermediate electronics between theIC chip and the external facility 138 may be for any of the applicationsdescribed herein.

In passive RFID tags 102, the maximum power transfer may be a criticalfactor in achieving the best performance in terms of operating (e.g.reading from and writing to) a tag. In order to facilitate the maximumpower transfer, the input impedance of the IC chip may be matched to thecorresponding antenna 108 input. In embodiments, a super strap mayprovide a desired flexibility in terms of matching multiple loads to asingle antenna 108. Thus, the antenna 108 may better deliver power toall IC chips on a super-strap. A series, parallel, series-parallel, orthe like interconnection configuration may provide for the most flexibleway of controlling and achieving the desired impedance of a super strap(i.e. load). Depending on the interconnect configuration the impedanceof a super strap may be controlled to achieve the desired value. Forexample, in the series connection there may be an improvement of thedelivered voltage sharing amongst networked ICs. Whereas, in theparallel arrangement of the IC chips on the super strap, there may be animprovement of the delivered current sharing among networked ICs.

In an embodiment, the RF network node 104 may be placed using conductiveinks. The RF network node 104 may be mixed into the conductive inksolution and deposited onto a RFID tag 102 substrate. The conductive inkapplications may be an ink jet application, a spray application, a brushapplication, silkscreen application, or the like. In an embodiment,there may be a controlled density of RF network nodes 104 within theconductive ink solution that allows a certain number of RF network nodes104 to be applied to the RFID tag 104 substrate with a certain volume ofconductive ink. For example, if a spray process is used, a spray of acertain duration may yield a known amount of RF network nodes 104 beingapplied to the RFID tag 102 substrate.

Referring to FIG. 12, an embodiment of a screen-printing method for theapplication of RF network nodes to a substrate is shown. In anembodiment, screen-printing may be the method of applying inks, dyes, orthe like onto a substrate through a mesh; the mesh may contain thepattern to apply the ink, dye, or the like. For example, screen-printingmay be used to apply ink or dye to cloth, apply circuits to a circuitboard, or the like. In an embodiment, the screen-printing process mayconsist of at least one ink, dye, or the like application to asubstrate.

In an embodiment, RF network nodes 104 may be in suspended a solution1204 for application through a mesh 1212 onto a substrate 1220. In anembodiment, the RF network node solution 1204 may be applied to the mesh1212 screen in preparation for being applied into the mesh openings1210. In an embodiment, the solution 1204 may include a conductivesolution, non-conductive solution, or other solution that may be usedwith a screen-printing process. In an embodiment, an applicator 1208 maybe used in a screen-printing method to move across the mesh 1212 todirect the solution into the mesh openings 1210. In an embodiment, themesh openings 1210 may be in substantially the same shape as the RFnetwork nodes 104. In an embodiment, the substantial matching of the RFnetwork nodes 104 and the mesh openings 1210 shapes may orient the RFnetwork node 104 to the substrate 1220 as the applicator 1208 directsthe RF network node 1202 into the mesh opening 1210. In an embodiment,the RF network node 104 may be any shape that may include round, square,rectangular, or the like.

In an embodiment, the antenna contacts for the RF network nodes 104 maybe on opposite faces of the RF network nodes 104. For example, theantenna contacts may be on the top and bottom faces of the RF networknodes 104. This embodiment may permit one antenna contact to connectwith the first antenna half and the second contact to be available forconnection to the second antenna half. In an embodiment, the shape ofthe RF network node 104 substantially matching the shape of the meshopening 1210 may facilitate the proper alignment of the RF network node104 with the substrate 1220 so that proper contact may be made with anantenna.

In an embodiment, the mesh 1212 may have at least one mesh opening 1210to create a pattern of RF network nodes 104 being placed on a substrate1220. In an embodiment, the dimensions of the mesh openings 1210, meshthickness 1214, mesh distance from the substrate 1218, the mesh shape,and the like may be configured to orient the RF network node 104 to thesubstrate 1220. For example, the RF network node 104 may be arectangular shape with the mesh 1212 having a similar rectangular shapeopening 1210. The mesh opening 1210 may be substantially the samerectangular shape and the mesh thickness 1214 may be matched to thethickness of the RF network node 1202. Thus, the mesh opening 1210 andthickness 1214 may act as a guide for the RF network node 104 to beproperly placed on the substrate. In an embodiment, the mesh tosubstrate distance 1218 may also be matched to the RF network node 104thickness so that only one RF network node 104 may be placed per meshopening 1210. It may be understood by those of skill in the art that anygiven mesh 1212 may contain more than one mesh pattern, or anyarrangement of mesh openings for the application of more than one RFnetwork node 104 pattern on the substrate 1220.

FIG. 13 depicts, in an embodiment, how screen-printed RF network nodes104 may be directed into contact with the substrate for proper antennacontact. If, after the screen-printing process is complete and the RFnetwork nodes 104 have been applied to the substrate 1220, the RFnetwork nodes 104 are not be in contact with the antenna, a RF networknode 104 may be directed into contact with the substrate. In anembodiment, the RF network nodes 104 may be directed to contact thesubstrate by methods that may include rolling, pressing, air pressure,suction, or other process capable of applying a force on the RF networknode 104 to make contact with the substrate 1220.

In FIG. 13, an embodiment of a rolling process to press the RF networknodes 104 into contact with the substrate is shown. As shown in view A,after screen-printing the RF network node 104 may be suspended in thesolution 1204 and not in contact with the substrate 1220. As depicted inthis figure, a roller 1302 may be used to roll over the screen-printedRF network node 104 pattern to press the RF network nodes 104 onto thesubstrate 1220. In an embodiment, the roller 1302 may rotate around acenter axis. In an embodiment, the roller may be made of a material thatwill not cause damage to the RF network node 104. In an embodiment, theroller material may include a silicone, rubber, or the like.

As shown in FIG. 13 view B, after the process to press the RF networknode 104 into contact with the substrate 1220, the RF network node 104may be in contact with the substrate 1220 and antenna. As shown in viewB, after the RF network node 104 has been pressed into contact with thesubstrate 1220, the solution 1204 may be cured with heat 1304 so thatthe RF network node 104 is fixed in its position relative to thesubstrate 1220.

Referring to FIG. 14, an embodiment of the screen-printing process ofapplying RF network nodes 104 to an antenna 108 is shown. In anembodiment, as shown in view A, the antenna 108 may be applied to thesubstrate 1220 using an inkjet process, screen-printing process, or thelike. In an embodiment, as shown in view B, the RF network nodes 104 maybe applied to the antenna 108 using the screen-printing as previouslydescribed in FIG. 12. In an embodiment, the screen-printing process maybe able to apply the RF network nodes 104 in a position required to makecontact with the antenna 108. In this case, the RF network node 104 maybe applied to one side of the antenna 108. In an embodiment, aspreviously discussed in FIG. 12, the RF network node 104 may have twoantenna leads that may be positioned on opposite sides of the RF networknode 104. In an embodiment, the screen-printing process may orient theRF network node 104 to position the RF network nodes 104 to thesubstrate 1220 providing for one of the RF network node 104 antennaleads to be in contact with the antenna 108. In an embodiment, as shownin view B of FIG. 14, one of the antenna leads may be in contact withthe left half of the antenna 108.

In an embodiment, after the RF network nodes 104 have beenscreen-printed in place and cured, a non-conductive layer 1404 may beapplied over the RF network nodes 104 to the other half of the antenna108 as shown in view C of FIG. 14. In an embodiment, the application ofthe non-conductive layer 1404 may be optional. In an embodiment, thenon-conductive layer 1404 may provide a transition material layer toallow a smooth contact path for a contact layer 1408 to follow. In anembodiment, the non-conductive layer 1404 may be a non-conductivesolution that may be applied by a process that may include ink jet,screen-printing, spray, brush, or the like.

In an embodiment, the contact layer 1408 may be applied to provide aconnection between the RF network nodes 104 and the other antenna half108 as shown in view D of FIG. 14. In an embodiment, the contact layer1408 may complete the circuit between one half of the antenna 108, theRF network node 104, and the second half of the antenna 108. In anembodiment, as shown in view D of FIG. 14, one RF network node 104 leadmay be in contact with the left side of the antenna 108, the second RFnetwork node 104 lead may be in contact with the contact layer 1408, andthe contact layer 1408 may be in contact with the right hand side of theantenna 108.

In an embodiment, the number of RF network nodes 104 applied to theantenna 108 may be related to the number of mesh openings 1210 that maycreate the pattern of the screen-printing mesh 1212, as describedpreviously with reference to FIG. 12. In an embodiment, the RF networknodes 104 may be applied to one side of the antenna 108, applied to bothsides of the antenna 108, bridge across the antenna 108, or may bearranged in any other orientation that allows the RF network node 104 tomake contact with both halves of the antenna 108.

In an embodiment, thermal printing may be another printing method thatmay be used for the application of multiple RF network nodes 104 to asubstrate, as shown in FIG. 15. FIG. 15 shows an embodiment of a thermalprinter ribbon 1502 applying ink, wax, resin, or the like to a substrate1504.

In an embodiment, the node network may comprise multiple RF networknodes 104 that are connected to communicate in a coordinated manner. Themultiple RF network nodes 104 may be connected as previously described,using a serial connection, parallel connection, antenna connection, orthe like. In an embodiment, thermal printing may be used in addition toother multiple network node application methods, such as screenprinting, or thermal printing may be a stand alone application thatapplies both the multiple RF network nodes 104 and the antenna 108.

In an embodiment, the thermal printer ribbon 1502 may be constructedusing at least two layers that may include a backing surface, an inksurface, and the like. In an embodiment, the ink may be a wax, resin, orthe like that may melt with the application of heat. In an embodiment, athermal element (not shown) may apply heat to the ribbon 1502 to meltthe ink surface and apply the ink to the substrate 1504. In anembodiment, the ink may be a conductive ink.

In an embodiment, the network nodes may be pre-applied to the substrate1504 using another application method. In an embodiment, the substrate1504 may be a continuous feed substrate on a roll, a set of individualsubstrates, or the like. In an embodiment, the substrate 1504 with themultiple network nodes may be fed into a thermal printer. In anembodiment the substrate 1504 may have antenna leads pre-applied to thesubstrate that may connect to the multiple network nodes. In anembodiment, the thermal printer may apply an antenna pattern to thesubstrate 1504 that may connect to the pre-applied antenna leads.

In an embodiment, the applied antenna pattern may be matched to the typeof container to which the RFID tag 102 is attached, including containersfor substances such as liquid, metal, wood, or the like. For example, ifthe RFID tag 102 is to be applied to a container for liquids, thethermal printer may print an antenna that performs best when in closerelation to a liquid. Similarly, the thermally printed antenna may beadapted for the surface of the container upon which it is printed, or itmay be adapted for the environment in which the container exists (e.g.,hot or cold conditions, humidity levels, proximity to corrosive gases orliquids, and the like).

As an example, the antenna pattern that may be printed onto thesubstrate 1504 may be selected from a set of antenna patterns that maybe used for the different materials on which the RFID tag 102 may beattached. In an embodiment, as a RFID tag 102 is being printed, theproper antenna may be selected from the set of antenna patterns based onthe object bearing the RFID tag 102. In an embodiment, the antennapattern that is printed may be different for each RFID tag 102 that isprinted. For example, a first RFID tag 102 that is applied to a waterbottle may receive an antenna that is suited for a water application,while the next printed RFID tag 102 that is applied on a metal containermay receive an antenna that is suited for the metal application. In anembodiment, the antenna pattern that may be printed on an RFID tag 102may be any antenna pattern chosen from the available antenna patternset.

It will be understood by skilled artisans that any type of information,such as bar code information, man readable information, or the like maybe printed on the RFID tag 102 by the thermal printer, in addition to anantenna pattern.

In another embodiment, the thermal printer may apply both the multipleRF network nodes 104 and the antenna pattern onto an RFID tag 102. In anembodiment, the multiple RF network nodes 104 may be applied to thethermal ribbon 1502 and may be applied along with a matched antennaduring the thermal printing of the RFID tag 102. In an embodiment, thesubstrate may be blank and all the RFID tag 102 components (e.g.multiple RF network nodes 104 and antenna 108) may be applied to theblank substrate. In this manner, the substrate may be any type of blanksubstrate to be applied to an object and the proper multiple RF networknodes 104 and antenna 108 may be applied as the RFID tag 102 is printed.

In an embodiment, the multiple RF network nodes 104 may have beenapplied to ribbon 1502, as shown in FIG. 15. In an embodiment, themultiple RF network nodes 104 may be applied using methods previouslydescribed methods such as screen printing, spray, brush, or the like. Inan embodiment, the multiple RF network nodes 104 may be applied in ageneric manner so that multiple RF network nodes 104 may be printedbased on the object to which the RFID tag 102 may be attached. Forexample, a first item may require a smaller amount of storage space forproduct data and therefore require fewer RF network nodes 104. A seconditem may be more complicated and may require more memory, functionality,and the like and therefore may require more RF network nodes 104. In anembodiment, the memory used for the second item may include public andprivate memory.

In an embodiment, the multiple RF network nodes 104 may be applied tothe ribbon 1502 using ink, wax, resin, or the like that hold themultiple nodes in place on the ribbon 1504. In an embodiment, during theprinting process the multiple RF network nodes 104 may be applied to thesubstrate by melting the ink, wax, resin, or the like that is holdingthe multiple RF network nodes 104 to the ribbon. In an embodiment, oncethe ink, wax, resin, or the like is melted, the multiple RF networknodes 104 may be applied to the substrate. In an embodiment, theconnections between the multiple RF network nodes 104 may also beapplied by the thermal printing process.

In an embodiment, the generic application of the multiple RF networknodes 104 may be a grid of RF network nodes 104 on the ribbon 1502applied to the substrate 1504 as required for the item that will bearthe RFID tag 102. For example, there may be an N×M grid of nodes on theribbon 1502 applied as required to create the multiple network nodes onthe substrate 1504. The multiple RF network nodes 104 required for aparticular application may require an N−3×M grid of RF network nodes 104to provide the application with the necessary memory and functionalityrequirements. The thermal printing process would apply the N−3×M nodesto form the multiple RF network nodes 104; the remainder of the nodesmay remain on the ribbon 1502.

In an embodiment, the thermal printer may apply an antenna 108 patternto the substrate 1504 that may connect to the multiple RF network nodes104 that may have been applied by the thermal printing.

When using ink or fluid RF network node 104 placement methods, the RFnetwork nodes may not be in contact with the antenna 108, may not beclose enough to the antenna 108, may not be in the correct orientationto the antenna 108, or the like. In these cases, as illustrated in FIG.16, the RF network nodes 104 may be pulled into contact with the antenna108 using a vacuum device 1618. Referring to FIG. 16, a method andsystem to provide a maximum number of randomly placed RF network nodes104 contacting the antenna leads 108 is shown. A vacuum device 1618 maybe used to pull the randomly placed RF network nodes 104 to the antennaleads 108 in the attachment zone 1610. This method may increase thepercentage of randomly placed RF network nodes 104 in electrical contactwith the antenna leads 108 in the attachment zone 1610. The attachmentzone 1610 may be where the leads from the antenna(s) 108 are in closeproximity to each other to allow contact with the randomly placed RFnetwork nodes 104. As previously described herein, the RF network nodes104 may be applied using a conductive ink method of depositing the RFnetwork nodes 104 to the attachment zone 1610. In embodiments, the RFnetwork nodes 104 may be applied by other random placement methods thatplace the RF network nodes 104 on the attachment zone 1610. In anembodiment, the RF network nodes 104 may be randomly placed in theattachment zone 1610 by any placement process.

The randomly placed RF network nodes 104 may not be flat on theattachment zone 1610, and therefore all the RF network nodes 104 may notmake an electrical connection with the antenna leads 1608. If theconductive ink application process is used, the RF network node 104 maybe partially on top of another RF network node 104. In an embodiment,the RF network nodes 104 may be angled between the antenna leads 1608and part of another RF network node 104. There may also be a pluralityof RF network nodes 104 suspended in the conductive ink solution and notclose enough to the antenna leads 1608 for the conductive ink to allowelectrical contact between the RF network nodes 104 and the antennaleads 1608.

As depicted in FIG. 16, a vacuum device 1618 may be used to draw RFnetwork nodes 104 that are not in contact with the antenna leads 1608into contact with the antenna leads 1608. In an embodiment, theattachment zone 1610 or the entire substrate 1602 may be made of aporous material 1614 that allows air or fluid flow through the porousmaterial 1614 using a vacuum device 1618. The vacuum device 1618 may beon the opposite side of the substrate 1602 from the RF network nodes1612 to draw air or fluid over the RF network nodes 104 and through theporous 1614 substrate 1602. The antenna 108 and antenna leads 1608 mayhave previously been applied to the porous 1614 substrate 1602. Thevacuum device 1618 may be used to draw air or fluids through the porous1614 substrate 1602 and may pull the RF network nodes 104 flat to theantenna leads 1608. To further aid the positioning of RF network nodes104 that are partially or fully on top of another RF network node 104,the substrate 1602 may be vibrated to allow the RF network nodes 104 tobe pulled flat to the antenna leads 1608. The substrate 1602 vibration,in conjunction with the vacuum device 1618, may allow the RF networknodes 104 that are partially or fully on top of other RF network nodes104 to move to a flat contact with the antenna leads 1608.

As previously described herein, and with reference to FIG. 2, the RFIDtag 102 may include at least one antenna 108 associated with themultiple RF network nodes 104. In embodiments, the multiple antennas maybe used to provide different antenna selections to match the type ofobject to which the RFID tag 102 is attached such as a metal object,liquid object, or the like. The RFID tag 102 may be able to select theantenna that provides the best reception and transmissioncharacteristics for the RFID tag 102 and object combination. In anembodiment, the RFID tag 102 may select one of the antennas to improvethe impedance match between the antenna 108 and the RF network nodes104, the object to which the RFID tag is attached may influence theantenna impedance.

In an embodiment, the at least one antenna 108 may be all the same typeof antenna, different types of antennas, a combination of similarantenna and different antennas, or the like. For example, an RFID tag102 that includes four antennas may have two pair of similar antennas.This may allow the RFID tag 102 a choice of two different types ofantenna for different object types (e.g. liquids or metals) and a choicewithin the antenna types to adjust the impedance of the selected antennatype to the RF network nodes 104. In an embodiment, there may be aplurality of different antenna designs that may be used on an RFID tag102 such as a bar antenna, a loop antenna, a patch antenna, and thelike. Additionally, in a multiple antenna configuration, the individualantennas may be shaped to simulate other antenna configurations. Forexample, more than one loop antenna may be applied in a circularconfiguration to simulate a patch antenna.

In an embodiment, the antenna 108 may have a plurality of antenna leadsin the area of the RFID tag 102 where the RF network nodes 104 areattached to the RFID tag 102. The antenna 108 leads may be of variousdesigns that may provide for small gaps between the two antenna 108halves. The small gap between the antenna leads may allow the RF networknode 104 leads to bridge the gap and make contact to both halves of theantenna 108. The two antenna 108 leads may branch into a plurality ofleads; the plurality of leads of the antenna 108 may be in closeproximity in the area on the RFID tag 102. This area on the RFID tag 102may be an area where the RF network nodes 104 are applied to the RFIDtag 102. In embodiments, the gap between the leads may be small enoughto allow the RF network node 104 to bridge the antenna 108 lead gap.

In an embodiment, the antenna 108 may be made of different materialssuch as metal, conductive inks, or the like. In embodiments, theconductive ink antennas 108 may be applied using ink jet, silkscreen,thermal printing, or the like, using, for example, a method that issimilar to the previously described conductive ink application of the RFnetwork nodes 108.

In an embodiment, the ink jet application of antennas may use a computerdevice to apply a selected antenna pattern to the RFID tag 102 usingconductive ink. The ink jet process may be similar to printing using astandard ink jet printer. In an embodiment, the selected antenna patternmay be stored in a database and at the time of the antenna 108 printing,the database may be searched to identify a suitable antenna for the RFIDtag 102. In an embodiment, the application of the antenna 108 mayinclude the application of the antenna leads, or the antenna leads maybe applied at a separate time.

In an embodiment, the silkscreen application of the antenna 108 may besimilar to the silkscreen application of RF network nodes 104 depictedin FIG. 12. There may be an antenna pattern provided in the mesh toapply the selected antenna. In an embodiment, the antenna 108 may beapplied at the same time as the RF network nodes 104 as part of thesilkscreen printing process.

In an embodiment, the thermal printing application of antennas 108 mayuse a thermal printer and ink ribbon to apply an antenna 108 to the RFIDtag 102, similar to the application thermal printing RF network nodes104 as described with reference to FIG. 15. In an embodiment, theselected antenna pattern may be stored in a database and at the time ofthe antenna 108 printing, the database may be searched to identify asuitable antenna for the RFID tag 102. In an embodiment, the applicationof the antenna 108 may include the application of the antenna leads orthe antenna leads may be applied at a separate time.

In an embodiment, the antenna 108 may be applied to the RFID tag 102substrate before the RF network nodes 104 are applied. As the RF networknodes 104 are applied to the antenna lead area of the RFID tag 102, theRF network node 104 antenna contacts may make a connection between theantenna leads for the two antenna halves, thereby making a completeconnection with the antenna 108. As previously described, the RF networknodes 104 may be precision placed onto the antenna leads or may berandomly placed on the antenna leads. In an embodiment, if a conductiveink process is used to apply the RF network nodes 104 to the antenna108, the antenna 108 may be applied at the same time using conductiveinks.

In another embodiment, the RF network nodes 104 may be randomly placedon the substrate before the antenna 108 and antenna leads are applied tothe substrate. The RF network nodes 104 may be randomly applied to thesubstrate using any random application process including one of theconductive ink application processes. In an embodiment, the antenna 108and antenna leads may then be applied over the RF network nodes 104; theantenna 108 and antenna leads may be applied at the same time or atseparate times. In an embodiment, the antenna leads may be applied usingone of the conductive ink processes. In an embodiment, the antenna leadsmay be applied using a non-intelligent application of the antenna leadsor an intelligent application of the antenna leads.

In an embodiment, the non-intelligent method of applying the antennalead pattern may involve applying the antenna leads in a preset patternregardless of the placement of the RF network nodes 104. By applying theantenna leads after the RF network nodes 104, the RF network nodes 104may not have to be completely flat on the substrate for the antennaleads to make contact with the RF network nodes 104 as the antenna leadsare applied over the RF network nodes 104. For example, the RF networknodes 104 may be positioned at an angle to the substrate but may stillmake contact with the antenna lead if the antenna lead is applied overthe RF network node 104 using the methods described herein. Thus, thismethod may yield a satisfactory percentage of RF network nodes 104 incontact with the antenna leads. It may be understood that this processmay connect a high percentage or some other percentage of the randomlyapplied RF network nodes 104 to the antenna leads.

In an embodiment, the RF network nodes 104 may be applied to the RFIDtag 102 substrate first and the antenna lead may be applied over the RFnetwork nodes 104 using an intelligent application process. In anembodiment, using the intelligent application of antenna leads, apattern recognition system may be used to recognize the position of theRF network nodes 108 on the substrate and may apply a unique antennalead pattern based on the placement of the RF network nodes 104. In anembodiment, a software application may determine the antenna leadpattern that may contact a maximum number of the RF network nodes 104, arequired number of RF network nodes 104, a minimum number of RF networknodes 104, or the like. It may be understood that not all of therandomly applied RF network nodes 104 may be connected to the antennaleads 1608 using this process. For example, some RF network nodes 104may not be accessible to the determined antenna lead 1608 pattern.

In an embodiment, the antenna pattern may be applied either before orafter the RF network nodes 104 are applied and may be matched to thetype of container or object to which the RFID tag 102 is attached,including containers for substances such as liquid, metal, wood, or thelike. For example, if the RFID tag 102 is to be applied to a containerfor liquids, the antenna that is applied may be selected from antennas108 that perform best when in close relation to a liquid. Similarly, theapplied antenna 108 may be adapted for the surface of the container uponwhich it is printed, or it may be adapted for the environment in whichthe container exists (e.g., hot or cold conditions, humidity levels,proximity to corrosive gases or liquids, and the like).

As an example, the antenna pattern that may be printed onto thesubstrate may be selected from a set of antenna patterns that may beused for the different materials on which the RFID tag 102 may beattached. In an embodiment, as a RFID tag 102 is being applied, theproper antenna may be selected from the set of antenna patterns based onthe object bearing the RFID tag 102. In an embodiment, the antennapattern that is applied may be different for each RFID tag 102. Forexample, a first RFID tag 102 that is applied to a water bottle mayreceive an antenna that is suited for a water application, while thenext RFID tag 102 that is applied on a metal container may receive anantenna that is suited for the metal application. In an embodiment, theantenna pattern that may be printed on an RFID tag 102 may be anyantenna pattern chosen from the available antenna pattern set.

In an embodiment, the set of antenna patterns may be a stored set ofantenna patterns in a database that may be applied by a conductive inkprocess, may be preprinted on the thermal ink ribbon to be selected atthe time of printing, may be a silkscreen pattern selected at the timeof printing, or the like.

In an embodiment, using a conductive ink antenna application method, theantenna type may be selected and printed when it is determined whichobject to which the RFID tag 102 will be attached. For example, on athermal ink printer, the user may use a computer device to indicate theRFID tag 102 will be applied to a certain object. As part of the RFIDtag 102 printing process, the computer device may search a database ofantenna patterns for a suitable antenna 108 to be applied to the object.Once the antenna 108 is selected from the database, the printer mayprint the selected antenna 108 pattern on the RFID tag 102. In thismanner, a suitable antenna 108 for use with the object may be printed onthe RFID tag 102 based on the indicated object.

The RFID tag 102 may interface with the reader 140, and include aplurality of functions, as shown in FIG. 17. The reader 140, sometimesreferred to as a scanner or interrogator, may include a radio frequencytransmitter and receiver 1714 that may both read and write informationto the RFID tag 102. The reader 140 may come in a plurality ofconfigurations, including fixed, portable, embedded, smart, or the like,for a plurality of functionality and applications. For example, a fixedreader 140 may allow for automatic data capture from a specificlocation, while a portable reader 140 may enable verificationfunctionality. In embodiments, the right combination of portable readers140 and fixed readers 140 may be important in maintaining the greatestvisibility of a RFID tagged 102 item throughout a supply chain. Anotherexample may be a smart reader 140, where the reader 140 may havefunctionality that allows the reader 140 to process and storeinformation associated with the RFID tag 102. Functionality included ina reader 140 may include a network interface 1702, a processor 1704, amemory 1708, a firmware 1710, a control facility 1712, a transmitter andreceiver facility 1714, a reader antenna 1718, or the like.

In embodiments, the reader 140 may include the control facility 1712,the transmitter and receiver facility 1714, and the reader antenna 1718as part of its core functionality. For example, the control facility1714 may provide for the control and flow of data to and from thetransmitter and receiver facility 1714, which may modulate anddemodulate data through the reader antenna 1718. The reader antenna 1718may in turn, provide for the RF communications interface to the RFIDtags' 102 antenna(s) 108. In embodiments, these three core functionalblocks may be an integral part of the reader 140 configuration,providing its basic functionality. This basic functionality may includethe emitting of an RF carrier signal that may activate the RFID tag 102,enabling the RFID tag 102 to exchange data with the reader 140.

In embodiments, when a RFID tag 102 passes through a region where thereader 140 is actively transmitting an activating RF carrier wave, theRFID tag 102 may detect the reader's 140 activation signal, and powerup. Communications between the reader 140 and the RFID tag 102 may nowcommence. The reader 140 may transmit commands to the RFID tag 102 thatmay initiate a return of information. The information transmitted fromthe RFID tag 102 may be decoded, and passed to the processor 1704. Theprocessor 1704 may perform a plurality of processing steps on thereturned RFID tag 102 data, including filtering operations to reduce thenumerous, and often redundant, reads of the same RFID tag 102, to asmaller and more useful data set. In embodiments, the protocols forexchanging of information between the RFID tag 102 and the reader 140may be governed by international standards, national standards, privatestandards, proprietary standards, or the like.

In embodiments, the reader 140 may provide for an interface to thenetwork 152 by processing information through the computer server 202.The data collected from the RFID tag 102 may be transferred to thenetwork 152 resource, such as the mass data storage 144, the applicationservers 148, the markets 150, or the like. The network 152 resources mayprovide for market specific applications processing of data, collectedfrom a plurality of RFID tags 102 and/or from a plurality of locations.For instance, the reader 140 may collect data from the RFID tags 102 asthe RFID tag 102 enters the reader's 140 proximity. As an example, themarket 150 application may be associated with the tracking of inventoryin a supply-chain. The reader 140 may collect data as the product nearsthe reader, and may transfer the data to the network 152, through thereader's 140 network interface 1702 and the computer server 202. Theapplication server 148 may then transfer the data into the mass datastorage 144, and make the data available for use to the appropriatemarket 150. In embodiments, the ability of markets 150 to access datacollected from the plurality of RFID tags 102, through the plurality ofreaders 140, may be a powerful market tool in the collection andmanagement of information associated with the RFID tagged 102 items.

In embodiments, the reader 140 may provide for data processing orstorage as an embedded function of the reader 140. This functionalitymay provide for an intelligent reader 140, or smart reader 140, capableof providing data processing functions that may be independent, or inaddition to, the network 152 resources. Functional blocks that may beassociated with these additional capabilities may include the processor1704, the memory 1708, the firmware 1710, or the like. The processor1704 may be a central processor 1704, a digital signal processor 1704, anetwork processor 1704, or the like. The memory 1708 and the firmware1710 may be RAM, DRAM, ROM, PROM, EEPROM, Flash, or any other memorytechnology known to the art. In embodiments, the reader 140 embeddedprocessing and storage may enable data processing capabilities thatdistribute or localize processing that would otherwise be performed bythe network 152 resources. This may increase the speed and accessibilityof the RFID tag 102 data. Additionally, the reader 140 embeddedprocessing and storage may enable data processing capabilities that maynot be possible with the network 152 resources, such as real-timeprocessing of data for immediate local use, closed-loop processing inassociation with the RFID tag 102 processing capabilities, the RFID tag102 integrated mesh-network data distribution and transfer, or the like.In embodiments, intelligent capabilities of the reader 140 may beassociated with the distributed and/or shared processing and memorystorage capabilities of the multiple RF network node 104 RFID tag 102.

In embodiments, information stored in the reader's 140 memory 1708 maybe for a plurality of uses. Examples may include information transmittedfrom the RFID tag 102, and stored for future processing either withinthe reader 140 or by the network 152 resources; information transferredinto the memory 1708 from the network 152 resources, and used by thereader's 140 processor 1704; information transferred into the memory1708 from the network 152 resources, and subsequently transferred to oneor more of the RFID tags 102, or the like. In embodiments, thecombination of the reader processor 1704 and the memory 1708 may enablea plurality of processing capabilities that may be utilized inconjunction with the increased, multiple RF network node 104,functionality. For example, the smart reader 140, local to the number ofmulti-RF network node 104 tags 102, may provide for a distributedmonitoring and detection network. In this example, the RFID tags 102 mayutilize their extended processing capabilities to read, convert, andcompare the sensor 138A data interfaced to the RFID tag 102. The RFIDtags 102 may periodically provide the sensor 138A processed data to thereader 140 upon request. The reader 140 may utilize an embedded, stored,or downloaded processor 1704 capability to monitor collected sensor 138Adata. This may be based on parameter limits set by the network 152resources, such as the market 150 application. In this way, the market150 application may have many such reader 140 monitoring sites, but mayonly receive feedback from the reader 140 when parameter limits havebeen exceeded, thus decreasing the complexity of the market 150 datacollection system.

In embodiments, the firmware 1710 stored in the reader 140 may containfundamental operability routines and data for the reader 140, such ascommunication protocols for the network interface 1702, controlalgorithms for the control 1712 of the transmitter and receiver 1714,the processor 1704 initialization routines, or the like. The firmware1710 may be upgradeable to help ensure compatibility with futurestandards, and to changes in the reader's 140 market 150 applications.In embodiments, changes to the reader's 140 firmware 1710 may beassociated with the functionality and the market 150 applicationsembedded in the RFID tags 102.

In embodiments, the processing capabilities of the reader 140, and theprocessing capabilities of the RFID tag's 102 RF network nodes 104, mayenable system functionality beyond typical passive RFID devices. Forexample the extended functionality of the system may enable the RFID tag102 to have an extended contact with the reader 140, sometimes referredto as a session. Another example is the ability for the system tosupport encryption. Standard cryptographic techniques may require moreresources than are available with typical RFID devices. In embodiments,the increased functionality of the RFID tag 102 may better enable theuse of cryptographic techniques.

In embodiments, cryptography implemented between the reader 140 and theRFID tag 102 may prevent RFID tag 102 cloning, a form of security breachassociated with unauthorized reading and reuse of the RFID tag 102commands. Some of the RFID tags 102 may use a form of ‘rolling code’scheme, wherein the RFID tag 102 identifier information may change aftereach scan from the reader 140, thus reducing the vulnerability of theRFID tag 102 to previously stolen responses. More sophisticated devicesmay engage in challenge-response protocols where the RFID tag 102 mayinteract with the reader 140. In these protocols, secret RFID tag 102information may be sent over a secure communication channel between theRFID tag 102 and the reader 140, where the reader 140 issues a challengeto the RFID tag 102. The RFID tag 102 may respond with a result computedusing a cryptographic circuit keyed with some secret value. Suchprotocols may be based on symmetric or public key cryptography, asdescribed herein. Still other cryptographic protocols may protectprivacy against unauthorized readers 140. One major challenge insecuring the RFID tags 102 may be the shortage of computationalresources within the typical RFID device. In embodiments, the RFIDsystems described herein may provide greater resources, so that standardcryptographic techniques may be more easily implemented.

In embodiments, the reader 140 may be operating in proximity to aplurality of RFID tags 102, and within range of other readers 140. Insuch circumstances, anti-collision techniques may be employed.Anti-collision algorithms may permit the simultaneous reading of largenumbers of RFID tagged 102 objects, while ensuring that each of the RFIDtags 102 is read only once. The chance of interference of the tworeaders 140 attempting to interrogate the same RFID tag 102 may be smallif the bandwidth of the reader's 140 frequency is wide enough. The RFIDtag 102 collision in RFID systems may occur when multiple tags 102 areenergized by the reader 140 simultaneously, and reflect their respectivesignals back to the reader 140 at the same time. This problem may beseen when a large volume of RFID tags 102 are read together in the sameRF field. The reader 140 may be unable to differentiate between thesesignals; with the resulting RFID tag 102 collision causing contentionwithin the reader 140. When the reader 140 recognizes that RFID tag 102collision has taken place, it may send a special signal, sometimesreferred to as a gap pulse. Upon receiving this signal, each of the RFIDtags 102 may consult a random number generator 122 to determine theinterval to wait before sending its data. Since each of the RFID tags102 receives a unique number interval, the RFID tags 102 may send theirdata at different times.

The reader 140 collision may also occur in RFID systems when thecoverage area of one reader 140 overlaps with that of another reader140. This may cause signal interference, with the RF fields of two ormore readers 140 overlapping and interfering. Having the readers 140programmed to read at fractionally different times may solve this.

Another technique that may be used to avoid collisions is frequencyhopping. Frequency hopping is understood to be a technique useful forkeeping two or more readers 140 from interfering with each other whilereading the RFID tags 102 in the same area. For example, UHF readers 140in the United States may operate between 902 and 928 MHz, jumpingrandomly (or in a predetermined sequence) to frequencies in between 902and 928 MHz.

In embodiments, the reader 140 may only be able to communicate with theRFID tag 102 when the RFID tag 102 is in range. A number of factors mayaffect the distance from the reader 140, also known as read distance, atwhich a RFID tag 102 may be read. Examples may include the frequencyused for identification, antenna gain, orientation and polarization ofthe reader antenna 1718, orientation and polarization of the RFID tag's102 antenna 108, placement of the RFID tag 102 on the object to beidentified, or the like. In embodiments, the choice of modulation schemeused to communicate between the reader 140 and the RFID tag 102 maychange the effective read distance or communication data rate. Themodulation technique used in the demodulator 118 may be any modulationtechnique known to the art, such as ASK, PSK, FSK, QAM, or the like. Inembodiments, the systems and methods described herein may employ theability to change the modulation technique of the reader 140 and/or theRFID tag 102 as a way to increase read distance and/or data rate. Forinstance, the system may change the order of a QAM scheme to increase areception parameter, such as raising the QAM order to increase the bitrate when the RFID tag 102 is close to the reader 140, lowering the QAMorder to improve bit-error-rates when the RFID tag 102 is at anincreased distance from the reader 140, or the like. By accommodatingvarious modulation schemes, the system may be able to improve its datarate and/or its read range.

In embodiments, the reader 140 may provide resources and capabilitiesthat are associated with the increased resources and capabilities of theRFID systems described herein. For instance, the reader's 140 interfaceto the network 202 may better enable the RFID tag 102 to remainresponsive to the market 150 needs, even after the RFID tag 102 has beendeployed in application; the reader's 140 processor 1704, the memory1708, and the firmware 1710, may better enable the RFID tag 102 toprovide the market 150 pre-processing, localized processing, encryptionor the like; the reader's control 1712, transmitter and the receiver1714, and the reader antenna 1718, may better enable the RFID tag 102 tocommunicate at a plurality of different frequencies, a plurality ofsimultaneous frequencies, varying modulations to improve data rateand/or read range, or the like. In embodiments, the reader 140 mayprovide an extension of the RFID tag's 102 resources and capabilities,as well as providing an interface through which the RFID tag's 102resources and capabilities may be extended to the market 150applications.

Referring to FIG. 18, a method and system for providing increasedcapability for an RFID tag 102 using distributed architecture is shown.The increased capabilities may allow for different types of RFID memory(e.g. secure memory, extended memory), encryption engines, and the liketo be provided within a single RF network node 104.

In an embodiment, a wafer 1802 may be designed with a plurality ofindividual adjacent RF network nodes 104 to be combined into one largerincreased capacity RFID distributed RF network node 1808. The increasedcapacity RFID distributed RF network node 1808 may permit individual RFnetwork nodes 104 to be integrated to allow the functionality of theindividual RF network nodes 104 to be combined. The increased capabilityRFID distributed RF network node 1808 may be singulated out of the wafer1802 as a single combined RF network node 1808. In an embodiment, thewafer 1802 may include the same or a combination of different types ofRF network nodes such as individual RF network nodes 104, increasedcapacity RFID distributed RF network nodes 1808, and the like.

In an embodiment, the increased capability RFID distributed architectureRF network node 1808 may incorporate at least two contacts 1810 that maybe common to all or some of the individual RF network nodes 104. Thecommon contacts 1810 may be additional antenna contacts, power contacts,data bus contacts, connection to other RF network node contacts, or thelike. In an embodiment, the increased capability RFID distributed RFnetwork node 1808 may have internal data connections between theindividual RF network nodes 104 to allow communication of information tobe passed between the individual RF network nodes 104. The informationmay be memory data, commands, and the like.

In an embodiment, the individual RF network nodes 104 within theincreased capability RFID distributed RF network node 1808 may continueto function as individual RF network nodes 104 with individualfunctionalities and may store individual data, commands, information, orthe like. In this case the multiple individual RF network nodes 104within the increased capacity RFID distributed RF network node 1808 mayprovide data and information redundancy that may act the same as aplurality of individual RF network nodes 104.

In an embodiment, the individual RF network nodes 104 may be coordinatedwithin the increased capacity RFID distributed RF network node 1808 withone individual RF network node 104 acting as a master RF network node tocoordinate the functionality of the other individual RF network nodes104 as described herein.

In an embodiment, the individual RF network nodes 104 may be integratedinto the increased capacity RFID distributed RF network nodes 1808 withsome or all of the individual RF network nodes 104 combined for a largerfunctional capacity. In an embodiment, there may be more than onecoordinated set of individual RF network nodes 104 within the increasedcapacity RFID distributed RF network node 1808; this may provide formore than one functionality within the increased capacity RFIDdistributed RF network node 1808. The integration RF network nodes 1808may include internal connections between RF network nodes 104 forcommunication and combining of functionality of the individual RFnetwork nodes 104. In an embodiment, the increased functionalitycapability may include increased data storage that may be coordinatedwith the integrated RF network nodes 1808.

In an embodiment, the increased memory capability may allow fordifferent types of memory capabilities within the increased capacityRFID distributed RF network node 1808. In an embodiment, the memorycapabilities may include public and private memory locations. In anembodiment, one or more RF network nodes 104 may be coordinated tocontain data for public read and write. In an embodiment, one or more RFnetwork nodes 104 may be coordinated to contain data that may include asecure method for reading and writing the data. Depending on theapplication, the combination of different RF network nodes 104 (publicor secure) may vary to provide the required memory capability for aparticular application. In an embodiment, a single increased capacityRFID distributed RF network node 1808 may contain both public and securedata memory locations. In an embodiment, the public information mayinclude the item name, the amount of the item, the weight of the item,and the like. In an embodiment, the secure information may include theprice of the item, the owner information, the destination, and the like.In an embodiment, the secure information may require a particular readerthat may decrypt the secure information.

In an embodiment, the increased capacity RFID distributed RF networknode 1808 may provide additional encryption features to the standardfunctionality. For example, the different memory locations may beassociated to an encryption integrated circuit within the samedistributed architecture. A data read/write may first pass through theencryption function before performing the read/write of the RFID tagdata. In an embodiment, some public access memory may not be encryptedwhile other security memory may be encrypted.

An additional benefit to the increased capacity RFID distributed RFnetwork node 1808 configuration may be an increased predictability ofplacement on an antenna lead. The increase size of the increasedcapacity RFID distributed RF network node 1808 may provide for the RFnetwork node more predictably to be flat to the substrate. The increasedlength may also allow for more predictability of the RF network nodecontacts connecting with the antenna leads.

Referring to FIG. 19, three embodiments of RF network node communicationmethods between RF network nodes 104 or other functional network nodesare shown. The RF network node 104 may be able to provide a signal to anadditional function network node 1908 using an additional lead 1904, twoor more RF network nodes 104 may be able to communicate in a serialmeans 1914, or two or more RF network nodes 104 may be able tocommunicate using a parallel means 1922. The added RF network node 104communication may provide additional functionality, function sharingbetween RF network nodes 104, memory combination, or the like. The RFnetwork nodes 104 communication may provide for communication ofcommands from a master RF network node 104, redundancy of functions ormemory, increased memory capability, or the like.

In View A of FIG. 19, an embodiment of a RF network node 104communicating with an antenna 108 and an external additional functionnetwork node 1908 is shown. The RF network node 104 may contain at leastone additional lead 1904 that may be connected to at lease oneadditional function network node 1908 that may provide an additionalfunctionality to the RF network node 104. The additional functionnetwork node 1908 may be a different type of network node or may beanother RF network node 104. The type of additional function networknode 1908 may include an encryption network node, a decryption networknode, master network node, impedance matching network node, securitydata network node (e.g. secure password and data storage), memorynetwork node, and the like. In an embodiment, the additional functionnetwork node 1908 may be an integrated circuit, a processor, amicroprocessor, a microcontroller, or the like.

In embodiments, the RF network node 104 may receive a read requestthrough the antenna 108 from an RFID reader 140. The RF network node 104may communicate with the additional function network node 1908 before orduring the return transmission to the reader. For example, whencommunicating secure data, the RF network node 104 may request anencryption or decryption of the data to be transmitted to the reader140. In another example, the additional function network node 1908 mayact as a master RF network node 104 and coordinate the communication ofinformation contained in at least one RF network node 104.

In embodiments, the RF network node 104 may contain logic to determinewhen to communicate with the additional function network node 1908 orthe RF network node 104 may communicate with the additional functionnetwork node 1908 with every read request.

In embodiments, there may be more than one additional lead 1904 to morethan one additional function network node 1908. In an embodiment, the RFnetwork node 104 may contain logic to determine with which of the morethan one additional function network nodes 1908 to communicate. In anembodiment, each additional lead 1904 may be connected to more than oneadditional function network node 1908. In an embodiment, the more thanone function network node 1908 may provide a function redundancy.

In View B of FIG. 19, an embodiment of at least two RF network nodes 104with a serial connection 1914 between the RF network nodes 104 is shown.This serial connection 1914 may act as a serial bus permitting the RFnetwork nodes 104 to communicate information. The communicatedinformation may be memory data, synchronization data, command data, orthe like.

In an embodiment, the serial connection 1914 may be a communication busthat may permit the individual RF network nodes 104 to coordinatefunctions. In an embodiment, there may be a master RF network node thatmay provide commands for the other RF network nodes 104. In anembodiment, each of the individual RF network nodes 104 may containcommunication logic to coordinating data reads and writes from the RFIDtag 102; the coordination may include time slot transmission for each RFnetwork node 104, memory combination, function combination, or the like.

In an embodiment, the serial connection 1914 may allow the individual RFnetwork nodes 104 to perform as a single RF network node 104. Forexample, all of the individual RF network nodes 104 may combine memorylocations by communicating memory information through the serialconnection 1914. In an embodiment, the memory locations may be combinedusing a master RF network node

In an embodiment, the serial connection 1914 may allow the individual RFnetwork nodes 104 to perform as a combined memory location. The combinedmemory locations may be at least two RF network nodes 104 coordinated tostore information. In an embodiment, there may be a plurality ofcombined memory locations within an RFID tag 102. In an embodiment, theplurality of combined memory locations may contain different types ofinformation (e.g. public or secure), redundant information, informationfor more than one item or product (e.g. more that one type of product ona pallet), different aspects of information about an item, or the like.For example, an RFID tag 102 may contain N combined memory locations;each may be capable of storing information about N items on a singlepallet. This may permit having N mixed items on a pallet and having justone RFID tag 102 on the pallet to track the N items. In an embodiment, amaster RF network node may control each of the plurality of combinedmemory locations; there may be a plurality of master RF network nodes inan RFID tag.

In an embodiment, the at least two RF network nodes 104 may be separatedor may be in contact with each other. In an embodiment, if the RFnetwork nodes 104 are in contact, they may form a single larger RFnetwork node 104; the single larger RF network nodes 104 may be able tocommunicate in a serial manner with each other to combine functions ormemory capabilities.

In an embodiment, if the RF network nodes 104 are separated, they may berandomly placed in a serial connection zone where the serial connection1914 leads may be in close relation to each other. In an embodiment, therandomly placed RF network nodes 104 may make contact with the serialconnection 1914 leads in a similar manner as making contact with antennaleads as described herein. In an embodiment, the serial connection zoneleads may be connected to the antenna leads.

In View C of FIG. 19, an embodiment of at least two RF network nodes 104having connections between the RF network nodes 104 to create a parallelcommunication connection 1922 is shown. This parallel connection 1922may act as a parallel bus that may permit the RF network nodes 104 tocommunicate information. The communicated information may be memorydata, synchronization data, command data, or the like.

In an embodiment, the parallel connection 1922 may be a communicationbus that may permit the individual RF network nodes 104 to coordinatefunctions. In an embodiment, there may be a master RF network node, asdescribed herein, which may provide commands for the other RF networknodes 104. In an embodiment, each of the individual RF network nodes 104may contain communication logic to coordinating data reads and writesfrom the RFID tag 102; the coordination may include time slottransmission for each RF network node 104, memory combination, functioncombination, or the like.

In an embodiment, the parallel connection 1922 may allow the individualRF network nodes 104 to perform as a single RF network node 104. Forexample, all of the individual RF network nodes 104 may combine memorylocations by communicating memory information through the parallelconnection 1918. In an embodiment, the memory locations may be combinedusing a master RF network node.

In an embodiment, the parallel connection 1922 may allow the individualRF network nodes 104 to perform as a combined memory location. Thecombined memory locations may be at least two RF network nodes 104coordinated to store information. In an embodiment, there may be aplurality of combined memory locations within an RFID tag 102. In anembodiment, the plurality of combined memory locations may containdifferent types of information (e.g. public or secure), redundantinformation, information for more than one item or product (e.g. morethat one type of product on a pallet), different aspects of informationabout an item, or the like. For example, an RFID tag 102 may contain Ncombined memory locations; each may be capable of storing informationabout N items on a single pallet. This may permit having N mixed itemson a pallet and having just one RFID tag 102 on the pallet to track theN items. In an embodiment, the master RF network node may control eachof the plurality of combined memory locations; there may be a pluralityof master RF network nodes in an RFID tag 102.

In an embodiment, there may be common connections 1920 between the RFnetwork nodes 104. In an embodiment, the common connections 1920 may beprovide connections to the antenna leads, power, additional functionnetwork nodes 1908, or the like.

Referring to FIG. 20, an embodiment of using the number of active RFnetwork nodes 104 match the antenna impedance 2008 is shown. Placing anunknown number of multiple RF network nodes 104 on a known antenna orthe placement of RF network nodes 104 on an antenna with an unknownimpedance, an impedance mismatch may be created that may reduce theability to energize the RF network nodes 104. In an embodiment, theimpedance 2004 of the combined RF network nodes 104 may be adjusted tocompensate for some of the antenna impedance 2008 mismatch.

In the application of the RF network nodes 104 to the RFID tag 102, theantenna 108 or the surrounding environment may not be a constant andtherefore the impedance may change with each situation. For example, RFnetwork nodes 104 may be used with various antenna designs with variousimpedances. In another example, an RFID tag 102 may be placed on itemssuch as liquids and metals that may change the impedance of the RFID tag102 antenna 108. In addition, in multiple RF network node 104 RFID tags102 the impedance of the combined RF network nodes 104 may not be aconstant depending on the number of active RF network nodes 104 on theRFID tag 102.

Referring to View A of FIG. 20, an antenna 108 may have an impedance ofZa 2008. In an embodiment, the antenna impedance 2008 may not beconstant for each application of the RF network node 104. For example,many different enterprises that may use different and unique antennas onthe RFID tags 102 may use the RF network nodes 104. The differentantennas 108 may present different impedance 2008 to the RF networknodes 104.

Additionally, having more RF network nodes 104 that are active on anRFID tag 102 may affect the impedance created by the RF network nodes104. In an embodiment, with the random placement of RF network nodes 104on an RFID tag 104, a variable number of RF network nodes 104 may beactive depending on the number of RF network nodes 104 making contactwith the antenna leads. For example, a first tag may have N active RFnetwork nodes 104 while a second tag may have M active RF network nodes104 (where N≠M). Each of these RFID tags 102 may have different RFnetwork node impedance 2004 but may be associated with the same type ofantenna 108. The impedance of the RF network nodes 2004 may be the totalimpedance of all the active RF network nodes 104.

In order to properly energize the passive RF network nodes 104 in theRFID tag 102, the antenna impedance 2008 must be matched to theimpedance 2004 of the RF network nodes 104 on the RFID tag. Za=Zc; whereZc is the equivalent impedance of all the active RF network nodes 104.

Referring to View B of FIG. 20, the RF network nodes 104 on an RFID tag102 may have their impedance Zc 2004 matched to the antenna 108 byadjusting the impedance of the RF network nodes 2018 (impedance matchingblock). This may be accomplished by the use of a logic RF network node2012 that may be able to send a control command 2014 to the impedancematching block 2018. The command may be to adjust the impedance of theRF network nodes 104. The adjustment of the active RF network nodes 104may adjust the total impedance 2004 of the impedance matching block 2018and therefore attempt to make an optimal impedance match with theantenna 108.

In an embodiment, the impedance matching block 2018 may be a set ofindividual RF network nodes 104 or may be a RF network node 104 groupconnected by a serial, parallel bus, antenna bus, or the like. In anembodiment, the control command 2014 may be a number that relates to thenumber of switch elements to turn on or off in the impedance matchingblock 2018. In an embodiment, the control command 2014 may be a functioncommand that is executed by the impedance matching block 2018 that mayresult in switch elements being turned on or off. In an embodiment, thelogic RF network node 2012 may make the determination of the number ofswitch elements to turn on or off in the impedance matching block 2018.In an embodiment, the logic RF network node 2012 may send more than onecontrol command 2014 for the adjustment of the impedance matching block2018. For example, there may be a control command 2014 sent after eachread attempt by the RFID tag reader 140.

In an embodiment, the RFID reader 140 may have an algorithm to receivethe RFID tag 102 transmissions, measure the strength of the response,calculate a command function, and resend the read signal with thecommand function. The command function may be a command to adjust theRFID tag 102 impedance and resend the RFID tag 102 data. The commandfunction may be received by the logic RF network node 2012, the logic RFnetwork node 2012 may determine the control command 2014 to be sent tothe impedance matching block 2018 to turn switch elements on or off tomatch the impedance of the antenna 108. An improved impedance match mayresult in the improved strength RFID tag 102 second return signal. In anembodiment, the process of the RFID tag reader 140 sending a readrequest and a function command to adjust the RFID tag 102 impedance maybe repeated until an acceptable RFID tag 102 transmission strength isachieved.

Aspects of the systems and methods described herein may be used in manydifferent markets 150 where material, parts, products, processes, andthe like may benefit from history tracking, movement tracking,identification, data recording, or other recording information on anRFID tag 102. Referring to FIG. 21, market 150 examples may includecommercial markets 2102, industrial markets 2104, consumer markets 2108,government markets 2210, agriculture markets, 2112, military markets2114, and medical markets 2118. These markets 150 are described in moredetail herein. It may be understood by a person with ordinary skill inthe art that other markets 150 may benefit from the increasedcapabilities of the RFID tag 102 systems and methods described hereinand this list of markets is not to be considered a limiting list ofmarkets.

Aspects of the systems and methods described herein may be used in manydifferent commercial markets where material, parts, products, processes,and the like may benefit from history tracking, movement tracking,identification, data recording, or other recording information on acommercial RFID tag 2102. Referring to FIG. 22, commercial marketexamples may include retail food 2202, retail general merchandise 2204,retail service stations 2208, retail physical plant 2210, retail hotelsand resorts 2212, restaurant food service 2214, employee identification2218, security systems 2220, airline management 2222, marine andshipping 2224, office management 2228, communication systems 2230,public events 2232, or the like.

The commercial RFID tag 2102 may be connected to a network where thenetwork connection may be a wireless connection, a wired connection, orthe like. The network with which the commercial RFID tag 2102 maycommunicate, may be a LAN, a WAN, a peer-to-peer network, an intranet,an Internet, or the like. The network connection may use the gatewayfacility 138C discussed in FIG. 11.

An aspect of the systems and methods described herein may be related tothe commercial RFID tag 2102 associated with a retail object and maystore and communicate commercial RFID tag 2102 information related toretail food 2202. The retail food 2202 may be a perishable product, anon-perishable product, or the like. The commercial RFID tag 2102 may beconnected to a sensor; the sensor may be a temperature sensor, ahumidity sensor, an acceleration sensor, or the like for recordinginformation on the environmental conditions in which the food 2202 isstored and transported.

The commercial RFID tag 2102 may be attached to a container of theretail object. The commercial RFID tag 2102 may be attached directly tothe container, or the commercial RFID tag 2102 may be attached to anRFID tag substrate and the RFID tag substrate may be connected to thecontainer. Additionally, the commercial RFID tag may be attacheddirectly to the retail object.

With the commercial RFID tag 2102 associated with retail food 2202, thestored information may be an expiration date, at least onetransportation date, at least one enterprise, or the like. The storedinformation may provide a transportation history of the retail food 2202along with freshness information of the food 2202.

In an embodiment, the stored information may contain information as aresult of a calculation where the calculation uses information that maybe stored on the commercial RFID tag 2102. In an embodiment, the storedinformation may be in the commercial RFID tag 2102 memory, stored in thecommercial RFID tag 2102 firmware, or the like. In an embodiment, thestored information may contain information as a result of informationmanipulation where the manipulation information uses information thatmay be stored on the commercial RFID tag 2102. In an embodiment, thestored information may be in the commercial RFID tag 2102 memory, storedin the commercial RFID tag 2102 firmware, or the like. In an embodiment,the stored information may contain information as a result ofinformation interpretation where the information interpretation usesinformation that may be stored on the commercial RFID tag 2102. In anembodiment, the stored information may be in the commercial RFID tag2102 memory, stored in the commercial RFID tag 2102 firmware, or thelike.

In an embodiment, the stored retail object information may containpricing information, retail pricing information, wholesale pricinginformation, discount pricing information, or the like. The storedinformation may contain quantity information; the quantity informationmay be changed, added, modified, or the like. Additionally, theinformation may contain quality information, point of sale check outinformation, return information, or the like.

In an embodiment, the stored retail object information may containpromotional information that may include a newspaper promotion, amagazine promotion, a mass mail promotion, a regional promotion, anational promotion, or the like. In an embodiment, the storedinformation may contain coupon information that may include a newspapercoupon, a magazine coupon, a mass mail coupon, a regional coupon, anational coupon, or the like.

An aspect of the systems and methods described herein may be related tothe commercial RFID tag 2102 associated with a service station purchaseand may store and communicate commercial 2102 RFID tag informationrelated to a service station purchase. The service station purchase maybe a gas purchase, a car supply purchase, a food purchase, a servicepurchase, or the like. In an embodiment, the stored information mayinclude an expiration date, at least one transportation date, at leastone enterprise, or the like.

In an embodiment, the stored information may contain a result of acalculation. The calculation may use information stored on thecommercial 2102 RFID tag. In an embodiment, the calculation informationmay be in memory, in firmware, or in the like. In an embodiment, theinformation may contain a result of information manipulation. In anembodiment, the manipulation may use information stored on thecommercial RFID tag 2102. The stored manipulation information may be inmemory, in firmware, or the like. In an embodiment the information maycontain a result from information interpretation. In an embodiment, theinterpretation may use information stored on the commercial RFID tag2102. The stored interpretation information may be in memory, infirmware, or the like.

In an embodiment, the stored information may contain service station2208 pricing information that may include retail pricing information,wholesale pricing information, discount pricing information, or thelike. In an embodiment, the stored information may contain quantityinformation; the quantity information may be changed, added, modified,or the like. In an embodiment, the stored information may containquality information, point of sale check out information, returninformation, promotional information, or the like. The promotionalinformation may be a newspaper promotion, a magazine promotion, a massmail promotion, a regional promotion, a national promotion, or the like.In an embodiment, the stored information may contain coupon information.The coupon information may be a newspaper coupon, a magazine coupon, amass mail coupon, a regional coupon, a national coupon, or the like.

In an embodiment the stored information may contain service agreementinformation, warranty agreement information, or the like.

An aspect of the systems and methods described herein may be related tothe commercial RFID tag 2102 used for storing and communicatingcommercial RFID tag 2102 information related to physical plantmanagement 2210. The physical plant may be a retail mall, a retailstore, a warehouse, a manufacturing facility, an industrial facility, orthe like.

In an embodiment, the commercial RFID tag 2102 may be connected to asensor for recording information related to physical plant management2210. In an embodiment, the sensor may be a temperature sensor, ahumidity sensor, an acceleration sensor, a smoke sensor, a carbondioxide sensor, a carbon monoxide sensor, or the like. In an embodiment,the sensor may be used to remotely record environmental conditions withthe physical plant 2210.

In an embodiment, the stored commercial RFID tag 2102 information may berelated to personnel identification. The RFID tag may track the egressand ingress of personnel within the physical plant.

In an embodiment, the stored commercial RFID tag 2102 information may berelated to supply ordering. The supply ordering may be manual,automatic, semi-automatic, or the like for ordering supplies for thephysical plant 2210 based in material information stored on thecommercial RFID tag 2102.

In an embodiment, the stored commercial RFID tag 2102 information may berelated to maintenance information. The commercial RFID tag 2102 may beassociated with an object or device that requires maintenance within thephysical plant 2210. The commercial RFID tag 2102 sensor may monitor andmeasure a maintenance characteristic related to the physical plant 2210.

In an embodiment, the commercial RFID tag 2102 information may berelated to physical plant 2210 security where the commercial RFID tag2102 tracks the egress and ingress of personnel within a physical plant2210 facility.

An aspect of the systems and methods described herein may be related tothe commercial RFID tag 2102 used for storing and communicatingcommercial RFID tag 2102 information related to hospitality enterprisemanagement 2212. The hospitality enterprise 2212 may be a hotel, amotel, an inn, a bed and breakfast, a resort, or the like.

In an embodiment, the hospitality enterprise 2212 information may berelated to check-in, an automatic check-in, check-out, automaticcheck-out, a hospitality enterprise service purchase, a hospitalityenterprise supplied device, or the like.

In an embodiment, the commercial RFID tag 2102 may be a credit card, ahospitality enterprise rewards card, a loyalty card, or the like.

An aspect of the systems and methods described herein may be related tothe commercial RFID tag 2102 used for storing and communicatingcommercial RFID tag 2102 information related to food service enterprisemanagement 2214. The food service enterprise 2214 may be a restaurant, abar, a caterer, or the like. In an embodiment, the commercial RFID tag2102 may be related to a credit card, a food service enterprise rewardscard, a loyalty card, or the like.

In an embodiment, the restaurant food service 2214 information may berelated to quantity of a food service product, a value of the foodservice product, an expiration date of the food service product, a foodservice product ordered by a customer, at least one enterprise, or thelike.

The restaurant food service 2214 information may contain a result of acalculation. The calculation may use information stored on thecommercial RFID tag 2102. The stored calculation information may be inmemory, in firmware, or the like. In an embodiment, the restaurant foodservice 2214 information may contain a result of informationmanipulation. The manipulation may use information stored on thecommercial RFID tag 2102. The stored manipulation information may be inmemory, in firmware, or the like. The restaurant food service 2214information may contain a result of information interpretation. Theinterpretation may use information stored on the commercial RFID tag2102. The stored interpretation information may be in memory, infirmware, or the like.

In an embodiment, the restaurant food service 2214 information may berelated to pricing information. The pricing information may be retailpricing information, wholesale pricing information, discount pricinginformation, or the like. The restaurant food service 2214 informationmay contain quantity information; the quantity information may bechanged. The restaurant food service 2214 information may contain pointof sale check out information, return information, or the like.

In an embodiment, the restaurant food service 2214 information maycontain promotional information. The promotional information may be anewspaper promotion, a magazine promotion, a mass mail promotion, aregional promotion, a national promotion, or the like.

In an embodiment, the restaurant food service 2214 information maycontain coupon information. The coupon information may be a newspapercoupon, a magazine coupon, a mass mail coupon, a regional coupon, anational coupon, or the like.

An aspect of the systems and methods described herein may be related tothe commercial RFID tag 2102 associated with employee identification2218 and may store and communicate commercial RFID tag 2102 informationrelated to the employee identification 2218. In an embodiment, theemployee identification 2218 may be an employee badge, an employee card,or the like. Additionally, the employee identification 2218 may beincorporated within part of an employee uniform such as a hat, a coat, ashirt, an apron, or the like.

In an embodiment, commercial RFID tag 2102 information may be related toemployee identification 2218 within an enterprise, employeeidentification during egress from an enterprise, employee identificationduring ingress to an enterprise, or the like. In an embodiment, thecommercial RFID tag 2102 information may be related to tracking employeework time such as a time card. In an embodiment, the commercial RFID tag2102 information may be related to associating an employee with atransaction such as a point of sale.

In an embodiment, the commercial RFID tag 2102 may contain informationrelated to employee identification 2218 during ingress and egress froman enterprise parking facility. This may provide information on thelocation of the employee within the enterprise or providing for safeentrance and exit from a parking facility.

An aspect of the systems and methods described herein may be related tothe commercial RFID tag 2102 associated with an identification deviceand may be used for storing and communicating commercial RFID tag 2102information related to a security system 2220 identification. Theidentification device may be a badge, a card, a part of clothing, a partof a vehicle, or the like.

In an embodiment, the security system 2220 information may be related topositioning of an object within a location, to positioning of a personwithin a location, to identification during egress from a location, toidentification during ingress to a location, or the like.

In an embodiment, the commercial RFID tag 2102 may be associated with asound facility. The commercial RFID tag 2102 may command the soundfacility to emit a noise when the identification device may be locatedexternal to a permitted location.

In an embodiment, the security system 2220 commercial RFID tag 2102 maybe used with a food service, a hospitality enterprise, a physical plant,a service station, employee identification, an aircraft, a ship, anoffice, a public event, or the like.

Additionally, the commercial RFID tag 2102 may be used with a vehiclesecurity system 2220 for information related to vehicle tracking. In anembodiment, the information may relate to a location of a vehicle, aningress of a vehicle to a location, an egress of a vehicle from alocation, a product transported by the vehicle, a mileage of thevehicle, a driver of the vehicle, an enterprise that owns the vehicle,and the like.

An aspect of the invention may be related to the commercial RFID tag2102 associated with a vehicle and may be used to store and communicatecommercial RFID tag information related to vehicle maintenance. Theinformation may relate to a vehicle maintenance, a next required vehiclemaintenance, a type of maintenance performed, a type of maintenance tobe performed, or the like.

In an embodiment, the commercial RFID tag 2102 may receive informationfrom a vehicle communication network. The received information may belubrication information, a fault notification, a part associated withthe fault, or the like.

Aspects of the systems and methods described herein may be used in manydifferent environments where material, parts, products, processes, andthe like may benefit from history traceability, movement tracking,identification, data recording, or other information recordinginformation. One environment may be the aviation 2222 industry, whereinformation may be tracked for individual components, assemblies,systems, or the like for quality, safety, traceability, servicetracking, maintenance tracking, counterfeit part prevention, life cyclemanagement, identification, or the like. While the aviation industry maypresently collect and store information on hardcopy or internal datastores, the hardcopy or data stores may not follow the component orsystem through the components life cycle making it difficult to verifythe history of a component at the point of use. Additionally, the lifecycle of an aviation component may be twenty years or more undervariable, often harsh conditions. As a result, the environment requiresdurable recording devices for maintenance of life cycle information. Thelife cycle information to be recorded may include date of production,dates of maintenance, in-use dates, amount of time in service, number offlight cycles, quality checks, information of the enterprise providingthe component or service, and the like.

In an embodiment, an aviation component may include a commercialcomponent RFID tag 2102 that may be used for the recording andmaintaining of information about the aviation component. Information maybe related to safety, component traceability, service tracking,maintenance, quality, counterfeit part prevention, life cyclemanagement, part identification, or the like.

In an embodiment, safety information may be related to airworthinesschecks at the component or system level, recording of service bulletins,maintaining the airworthiness document of the component, aircraftsecurity, or the like. In an embodiment, using commercial RFID tags2102, each component may be safety checked before a flight, at regularsafety check intervals, after a set number of flights, after a servicebulletin has been received, or the like to verify the compliance of thecomponent or set of components. The commercial RFID tag 2102 may containthe memory requirements to store all the safety information pertainingto the component for the life cycle of the component.

In an embodiment, the set of commercial RFID tag 2102 on an aircraft maybe used to verify the airworthiness of the aircraft before a flight. Forexample, there may be an aircraft safety check prior to takeoff whereall of the commercial RFID tags 2102 are read to verify theairworthiness of the entire aircraft system. This check may be performedat a certain location at the airport, by ground personnel before leavingthe loading gate, by an automatic check as part of the pilots preflightcheck list, or the like. In another embodiment, while at one of theaircraft check locations, the airworthiness of the aircraft may be readand verified by a person at a location remote from the aircraft such asby an airline enterprise quality center, a control tower, a centralairworthiness control center, or the like. The remote location may notbe located at the airport, but may be located at a distant facility thatmay monitor airworthiness of aircraft at one or more airports. In anembodiment, the aircraft may not be cleared for takeoff until theairworthiness of the aircraft was verified. In an embodiment, theverification may include a check for components beyond the permittednumber of flight cycles, proper airworthiness documentation, properlyfunctioning systems, and the like.

In another embodiment, commercial RFID tag 2102 at entry points to theaircraft may enhance aircraft security. In an embodiment, the aircraftentry points such as aircraft doors, cargo doors, maintenance accessdoors, or the like may have commercial RFID tag 2102 that may requireverification that the person attempting to gain access is authorized toopen the entry point. For example, a cargo door used for loadingpassenger luggage may have a commercial RFID tag 2102 that may recordthe identification of the personnel accessing the cargo door. In anembodiment, when the aircraft airworthiness check is performed, thecargo door may transmit identification of all personnel that accessedthe cargo door; the aircraft airworthiness may not be cleared if theidentification of all access personnel does not match a permissiblepersonnel list. In another embodiment, an aircraft access door may notunlock unless the personnel requesting access matches a list ofpermitted personnel stored on the commercial RFID tag 2102.

In another embodiment, commercial RFID tag 2102 associated with criticalcomponents may be constructed to survive catastrophic events such as anaircraft crash, component catastrophic failure, or the like. For theseaviation components, the commercial RFID tag 2102 may survive thecatastrophic event and be able to transmit the last recordedinformation; the information from the commercial RFID tag 2102 may beuseful in the catastrophic event investigation. For example, thecommercial RFID tag 2102 may provide rapid on location information onthe airworthiness of the various components, the flight cycles, maximumand minimum data points, part identification, maintenance history, anthe like. As another example, a commercial RFID tag 2102 associated witha critical component may be able to sense an overwhelming overrun ofsystem parameters such as would occur with a catastrophic component orsystem failure, and may collect information from a plurality of othercommercial RFID tag 2102 associated with critical components. Thisinformation may then be recorded and/or transmitted to an offsitelocation, so as to provide a snapshot of system wide component status atthe moment of crucial component failure.

In an embodiment, component traceability information may be related tothe type of repairs to a component, the repair history, tracking of thecomponent within an assembly of components, when a component is retiredfrom service, or the like. During the life cycle of a component manyactions such as repairs, component upgrades, reassemblies, or the likemay be performed on the component. The commercial RFID tag 2102 mayrecord information once the action has been completed, thereby providinga history of the actions performed on the component. The recordedinformation may provide for traceability of the actions back to a time,an enterprise, a repair, an assembly, or the like if there is a questionof the components airworthiness. For example, an airworthiness bulletinmay be received and an enterprise may need to determine if componentswithin the enterprise comply with the bulletin. All the enterprisescommercial RFID tags 2102 may be read for information related to thebulletin to verify the airworthiness of the enterprise's components.

In an embodiment, service tracking may be recorded on the commercialRFID tag 2102 to track the actual flight cycle information of acomponent such as the number of flight cycles of the components, thelatest flight cycle number of the component, storing the last service ofthe component, storing the next required service of the component, orthe like. Some aviation components may have requirements for inspectionsbased on the number of flight on which the component has been used. Inan embodiment, the commercial RFID tag 2102 may be associated with asensor to record flight parameters that may be indicative of a componentflight such as air pressure, temperature, component stress (e.g. landingforces), or the like. Using the sensor, the commercial RFID tag 2102 mayautomatically record the actual flight characteristics as applied to thecomponent. For example, a component may only be considered having aflight cycle if it experienced a certain stress load during the flight.If the certain stress load was exceeded, the commercial RFID tag 2102may record that the component has experienced a flight cycle. The numberof flight cycles may be read during the next data reading from thecomponent and may be compared to the flight cycle service requirements.

In an embodiment, component maintenance may be recorded on thecommercial RFID tag 2102 to track maintenance information about thecomponent such as the type of repair, the repair technician, the repairdates, the repair enterprise, or the like. In an embodiment, as thecomponent has maintenance (e.g. repair, upgrade), the maintenanceinformation may be recorded to the commercial RFID tag 2102 to provide amaintenance history of the component. In an embodiment, the maintenancehistory may be read from the commercial RFID tag 2102 any time duringthe components life cycle. For example, there may be a question of thetype of repair performed on a class of components and an enterprise maybe able to query all of their commercial RFID tag 2102 to determine ifany of the enterprise's components may have had this type of repair.This capability may provide the enterprise a rapid method of componentverification to quickly resolve a question of component airworthiness.

In aviation maintenance, repair, and overhaul facilities, aviationcomponents and aviation assemblies may undergo a number of maintenanceand repair cycles during the life cycle of the component or componentassembly. The components may have defects that have developed duringnormal operation. These defects may be repaired or sub-components of theaviation component may be replaced as part of the repair. The commercialRFID tag 2102 may be used to record the maintenance history of theaviation component during overhaul and repair of the aviation component.

During the life cycle of the aviation component, the commercial RFID tag2102 that is associated with the component may record the operationalhistory of the component such as the number of flight cycles, operatingenvironment, maintenance dates, maintenance history, and the like. Theincreased memory capability of the multi-RF network node 104 commercialRFID tag 2102 may allow for storing these various types of informationin segmented memory (e.g. set memory locations for each type ofinformation), redundant memory, protected memory, public memory, and thelike. The enhanced memory capabilities of the commercial RFID tag 2102may allow for the continuous storing of the operational history of thecomponent throughout the life cycle of the component.

A critical part of aviation component maintenance may be thedetermination of the cause of the operational defect to be repaired.There may be a number of quality protocols used to determine the causeof the defect such as a root-cause analysis. Root-cause analysisattempts to determine not just the immediate cause of the defect, butthe root manufacturing process or design characteristic that may havecontributed to the development of the defect. Root-cause analysisdepends on reviewing past history of the component that may include theOEM manufacture, operational parameters, previous maintenance, materialsused to produce the component, and the like. The commercial RFID tag2102 may store these types of information in its enhanced memory and maybe reviewed during the initial review of the component being repaired;the information stored on the commercial RFID tag 2102 may be read andreviewed as part of the root-cause analysis. The root-causedetermination may require the information from a number of components tobe reviewed, over time the operational history of components stored onthe commercial RFID tag 2102 may be aggregated for an analysis of aplurality of the same components for development of trends that maycontribute to component defects.

During the maintenance of the component, information may be written tothe commercial RFID tag 2102 to provide a maintenance history of thecomponent. As the repair is performed the commercial RFID tag 2102 mayrecord the mechanic performing the repair, the repair process performed,the date of the repair, the identification of the quality assurancepersonnel, materials used in the repair, and the like. The repairinformation may be written to the commercial RFID tag 2102 for everyrepair sequence performed, at the completion of the repair, at thecertification of the repair, or the like to form the maintenance historyof the repair. In an embodiment, each time the component is repairedduring its life cycle, the repair information may be written to thecommercial RFID tag 2102.

During the repair of the component, it may be determined to replace apart of the component, replace a sub-component, retire the component andprovide a replacement component, or the like. The replacement of thesub-components and parts of a component may be recorded on thecommercial RFID tag 2102 as part of the maintenance history of thecomponent. The recording of the replacement of the sub-component withina component assembly may provide for configuration control of thecomponent. For example, repairing an assembly may require replacing adamaged heat shield by installing a new heat shield into the assembly.When the new heat shield is installed into the assemble the newconfiguration information may include the new heat shield part number,serial number, manufacture date, or the like may be written to thecommercial RFID tag 2102 of the assembly. The information stored to thecommercial RFID tag 2102 may also include information about the damagedheat shield such as the part number, serial number, date of manufacture,date of removal from the assembly, and the like.

In an embodiment, the maintenance history of the component may beavailable to the airline enterprise, field maintenance personnel, FAAinspectors, or the like by reading the commercial RFID tag 2102maintenance information with a reader or portable reader. Themaintenance history may be read and verified by a maintenance enterprisethat is responsible for assembling the repaired component into anaircraft. The maintenance personnel may be able to read the commercialRFID tag 2102 to verify the repair performed, the mechanic performingthe repair, final FAA certification of the repair, or the like. Thereading of the information on the commercial RFID tag 2102 may also bestored into the configuration information for the entire aircraft toprovide configuration control for the aircraft. The maintenancepersonnel may be able to verify that the component should be assembledinto the aircraft by verifying that the part number of the component ispart of the aircraft configuration. This check may prevent a wrongcomponent from being assembled into an aircraft.

The commercial RFID tag 2102 may also be used to store Air TransportAssociation (ATA) Spec 2000 standards information. The ATA Spec 2000 isa comprehensive set of e-business specifications, products, and servicesthat are used to streamline the aircraft component supply chain.Information related to component maintenance, component history,component ordering, and the like may be written to and read from thecommercial RFID tag 2102 using the ATA Spec 2000 standard. The ATA Speck2000 information may be stored in XML format to allow rapid transmissionof information over a network, including the Internet. Information readfrom the commercial RFID tag 2102 may be transmitted to a network forincreased speed in ordering replacement components, requesting a repairof a component, aggregation of a components operational history, and thelike. In an embodiment, the XML formatted ATA Spec 2000 information maybe stored in the enhanced memory of the commercial RFID tag 2102.

In embodiments, the enhanced memory capabilities of the commercial RFIDtag 2102 may be a point-of-use information source, reduce maintenancecycle times, improve configuration management, improve componenttracking, increase asset value, improve product integrity, documentabuse/misuse, document no-fault-found history, and the like. Storingcomponent history information with the component may provide readilyaccessible critical component information that may be read at anypoint-of-use (e.g. at an aircraft). Maintenance cycle time andconfiguration control may be easily stored and maintained electronicallywith the component on the enhanced memory commercial RFID tag 2102 toallow verification of repairs and configuration control at the componentand aircraft level. Component tracking may be greatly enhanced bypermitting the commercial RFID tag 2102 to be read at a plurality ofaccess points in the distribution system, in storage, in the aircraft,or the like. Documenting the history of the component may prevent themisuse of components by providing information on the airworthiness of acomponent, information if the component has a valid serial number,verification if a component has been retired from service, and the like.Additionally, the documented history of a component, including theflight cycle history, may provide information to reduce theno-fault-found determinations when a component fault cannot bereproduced on the ground or away from the aircraft. Flight cycle historymay provide the needed information to successfully complete a root-causeanalysis and therefore may allow for a repair that may not have beenpossible without the stored information on the commercial RFID tag 2102.

In an embodiment, component quality information may be recorded on thecommercial RFID tag 2102 to track quality related information such asinspection dates, flight cycle tracking, component configuration,material information, supplier information, or the like. Thisinformation may be used in the quality confirmation of a component, usedin defect root cause analysis, verification of a proper assembly,comparing the components actual life cycle information with industry andFAA requirements, or the like. In an embodiment, quality controlpersonnel may be able to read the component quality information for anaircraft before a flight to verify that all of the components with thecommercial RFID tag 2102 are airworthy. Additionally, an aviationenterprise may be able rapidly to perform a quality check of all theiraircraft in response to a supplier notification, FAA request,airworthiness bulletin, or the like by reading all the commercial RFIDtags 2102 within their aircraft.

In an embodiment, the commercial RFID tag 2102 may be used incounterfeit part prevention by storing the component supplierinformation, component identification, component serial numbers, or thelike. Counterfeit parts may be produced by an enterprise that is notcertified to produce airworthy components, components produced fromother components that have been retired from service (e.g. scrapped), orthe like; a counterfeit part may not be airworthy. In an embodiment, anaviation enterprise may receive a component from a supplier. Thecomponent information may be read from the commercial RFID tag 2102 forverification that the part is airworthy and not counterfeit. Forexample, the received component information may be verified against acomponent database to verify the components identification, verify thatthe serial number is still an active serial number (e.g. not retired),view the history of the components life cycle, or the like.

In an embodiment, component life cycle management may be recorded on thecommercial RFID tag 2102 to allow tracking of the component's lifecycle. The life cycle management information may contain life cycleinformation from the original equipment manufacturer (OEM) to thecurrent time period, record past maintenance dates, future maintenancedates, particular flight information (e.g. stress levels), or the like.Life cycle management may be related to other aspects of the componentsuch as safety, maintenance, quality, or the like. In an embodiment, anaviation enterprise may be able to rapidly determine the status of thelife cycle of any or all components of an aircraft that has a commercialRFID tag 2102. For example, the aviation enterprise may periodicallyread all the commercial RFID tags 2102 on an aircraft to record the lifecycle information for the entire aircraft. The aviation enterprise mayuse the life cycle information to manage the maintenance schedules ofthe aviation enterprise's aircraft fleet.

In an embodiment, component identification may be recorded on thecommercial RFID tag 2102 to include the OEM information, repairenterprise information, component number, serial number, componentrevision level, or the like. This information may be applied as thecomponent is produced, revised, repaired, or the like to provide atraceable history of the manufacture of the component. The componentidentification may become the base information to allow the component tobe tracked though out the component's operational life cycle.

In an embodiment, the storing of information for the above capabilitiesmay be implemented using different memory configurations such as publicmemory, private memory, encrypted memory, read/write memory, writeonce/read many memory, read only memory, or the like. For example, thecomponent identification may have information that should not be changedsuch as component number and serial number, therefore the some or all ofthe component identification may be stored in write once/read manymemory. This would allow the OEM to write the component identificationbut not allow anyone else to change this information. In anotherexample, there may be enterprise only information that may be storedusing encryption memory so only the enterprise may read the information.It may be understood by someone knowledgeable in the art that the memoryof the commercial RFID tag 2102 may be configured based on therequirement of the commercial RFID tag 2102.

Aspects of the systems and methods described herein may be relatedstoring and communicating commercial RFID tag 2102 information relatedto maritime shipping 2224. In an embodiment the maritime shipping 2224information may be related to a location of a maritime ship such asingress and egress of the ship to and from a port.

In an embodiment, the maritime and shipping 2224 information may berelated to a cargo of the maritime ship. The cargo information may be atype of cargo, a quantity of cargo, an origin of the cargo, a finaldestination of the cargo, at least one interim destination of the cargo,a product, a pallet, a container, a ship, or the like.

An aspect of the systems and methods described herein may be related tostoring and communicating commercial RFID tag 2102 information relatedto a public event 2232. The public event may be a concert, a play, asporting event, a business conference, or the like.

The public event 2232 information may be related to ticket validation, apublic event date, a public event time, a number of tickets, a seatinglocation, a public event title, or the like. The public event 2232information may be related to admission to a public event, an admissiontaken manually at a gate, an admission taken automatically at a gate, orthe like.

Aspects of the systems and methods described herein may be used in manydifferent markets where material, parts, products, processes, or thelike may benefit from history traceability, movement tracking,identification, data recording, or other information recording andprocessing. Referring to FIG. 23, a market example may be the industrialfield, where product information and history may be tracked throughindustrial RFID tags 2104. Product information and history may befollowed through the entire life-cycle of the product, from thereceiving of raw materials to the shipment of finished goods for sale,including factory process 2302, factory inventory 2304, warehousesystems 2308, factory transportation 2310, industrial quality control2310, or the like. The use of industrial RFID tags 2104 as describedherein may significantly increase the ability of an industrial facilityto track the location and history of the final product, as well as thecomponents that are included as a part of the final product. Further,through access to location and history information for the product andits components, post-sale attributes may be tracked, such as productperformance, quality, reliability, return rate, customer complaints, orthe like. An industrial facility may feed these post-sale attributesback into the manufacturing process and product design to furtherimprove the quality of the product and reduce post-sale costs. The useof the systems and methods described herein may therefore contribute tothe future quality of the produced product.

The factory process 2302 may benefit from the systems and methodsdisclosed herein in a number of ways, including the identificationtracking of components and sub-assemblies included in the finalproduction product; the production history of the components andsub-assemblies of the final production product, such as the location ofmanufacture, the date of manufacture, the time of manufacture, thepersonnel that participated in the manufacture of the components andsub-assemblies, or the like; the transportation history of componentsand sub-assemblies; the tracking of the manufacturing process for thefinal production product, such as where it is in the process; thecontrol of the manufacturing process for the final production product,such as implementation of unique processing steps; the history of themanufacturing process for the final production product, such as the dateof production, the time-sequence of each subassembly process step,personnel involved in the production, or the like; the tracking ofissues encountered during production of the product; a history of allinspections performed on the product; date of final packaging of theproduct; or the like. In embodiments, the factory process 2302 may bemade more efficient and reliable due to the expanded capabilities of thesystems and methods described herein.

In embodiments, manufacturing control may be made more efficient throughthe use of the disclosed systems and methods. Manufacturing controlincludes factory processes 2302 that effect the production of a productbeing manufactured, such as what color the product is to be, selectionof optional features for the product, selection of optional processingsteps for the product, or the like. For example, in an embodiment, aproduct may have the option of being painted red, green, or blue. Theproduct may have an attached industrial RFID tag 2104. The product'sindustrial RFID tag 2104 may have been previously loaded with anidentification number and data to indicate what color the product is tobe painted. As the product is brought near the paint facility, thereader 140 may extract the identification number and color data, andsend that data to the painter. During the painting, various paintparameters, such as paint mix, spray time, temperature, or the like, mayby be recorded by the paint facility. Upon completion of the paintingstep in the manufacturing process, the paint parameters may bedownloaded onto the industrial RFID tag 2104 through the reader 140. Inthis way, the product that has been painted now may contain the paintparameters through its useful life. If the product was a car forexample, and the car showed premature rusting, the industrial RFID tag2104 may be accessed to help determine whether the painting duringmanufacturing may have contributed to the premature rusting. Inembodiments, the systems and methods described herein may be able toutilize RFID tag capabilities to not only control the manufacturingstep, such as painting, but also to record the conditions of manufactureto be stored on the industrial RFID tag 2104, and to stay with theproduct through its operational life.

In an embodiment, the product being manufactured may be a motherboard ofa personal computer. The motherboard containing an industrial RFID tag2104 may have options associated with it, such as amount of memory, typeof processor, clock speed, or the like, recorded in the memory of theindustrial RFID tag 2104. As the blank printed circuit board approachesthe component placement facility, the reader may access the industrialRFID tag 2104 for component information. The component placementfacility may then choose the appropriate components, and mount them onthe motherboard. Further, the component history for the parts placed onthe motherboard, such as part number, date code, lot code, or the like,may be recorded by the component placement facility. The componentplacement facility may write this component history to the industrialRFID tag 2104 attached to the motherboard. This information may staywith the motherboard through the remaining stages of manufacturing, andon through its operational life.

In embodiments, the industrial RFID tag 2104 may be read by a technicianto aid in the diagnosis of problems associated with the motherboard,either during test stages in manufacturing, or during the operationallife of the unit. In embodiments, the industrial RFID tag 2104 attachedto the motherboard may be able to communicate with an industrial RFIDtag 2104 associated with the higher assembly personal computer. Theindustrial RFID tag 2104 associated with the personal computer may haveaccess to an Internet interface, which may be used to monitor recalls orother issues related to the components on the motherboard. Further, thistype of informational connection between the industrial RFID tag 2104 onthe motherboard and the Internet may enable a technical support facilityconnected to the internet to extract information contained on theindustrial RFID tag 2104 on the motherboard. In embodiments, theindustrial RFID tag 2104 may utilize the capabilities of the systems andmethods described herein to aid in the control of manufacture, as wellas to record associated component and process history of the componentsto more efficiently diagnose future failures for issues associated withthe components.

In embodiments, the industrial RFID tag 2104 may be associated with themanufacturing of a material component that is formed from raw materialsand integrated into a larger assembly. One such example of such amaterial component may be a steel bridge member that is formed frommolten steel and integrated into a road bridge. In this instance, theforging and forming facility that manufactures the bridge member mayrecord the history information associated with the raw materials, theconditions and environments experienced during forming, post-formingperformance test results, or the like. This information may bedownloaded onto an industrial RFID tag 2104 that is mounted on thebridge member. This information may now be utilized in mechanicaltesting of the bridge member prior to shipment, as well as placementinformation on the site of the bridge assembly. Further, in embodiments,the information stored in the bridge member's industrial RFID tag 2104may be utilized during periodic bridge inspections, along withenvironmental information that may be collected by industrial RFID tags2104 associated with the entire bridge assembly.

In embodiments, tracking and location of manufacturing parts may be mademore efficient through the use of the systems and methods describedherein. Each part may be associated with an industrial RFID tag 2104,either by direct mounting, or through mounting to the part's packaging.The ability for a manufacturing facility to track and locate all of theparts within the facility may be advantageous to the efficiency of themanufacturing facility. For example, one of the most fundamental stepsin the assembly of a component may be the gathering of parts, sometimesreferred to as kitting, required to complete the assembly procedure. Ifan assembly is begun without all parts accounted for, the assembly mayhave to be halted, breaking the flow and time efficiency of theproduction line. The systems and methods described herein may aid in theautomated determination of whether a kit is complete or not, and if not,reporting shortages. With industrial RFID tags 2104 on all parts withinthe facility, it may become easier to locate parts that are needed,determine what assemblies have priority within the manufacturing flow,and move those parts in order to maintain a smooth running assemblyflow.

The systems and methods described herein may also better enable theaggregation of part histories. For instance, industrial RFID tags 2104associated with parts may contain history associated with those parts.As these parts are integrated into higher assemblies, their historiesmay be requested through readers 140 and transferred to an industrialRFID tag 2104 associated with the higher assembly. In this way, thehigher assembly's industrial RFID tag 2104 may contain the historyinformation of all the parts that make it up. In embodiments, thedisclosed systems and methods may have expanded capabilities to betterenable the tracking of information pertaining to an assembly's parts.

In embodiments, the tracking and location scheme that starts with partsor raw materials, may be extended up through the sub-assembly andassembly stages that lead to the finished product. For instance, anindustrial RFID tag 2104 may be associated with each part, with all itshistory and performance data written into the memory of its industrialRFID tag 2104. As the parts are integrated into sub-assemblies, anindustrial RFID tag 2104 may be attached and associated with eachsub-assembly. The sub-assemblies may get an identification number totrack and locate them, allowing the facility to track and locate aparticular sub-assembly to be kitted for the next level of assemblyintegration. In addition, the industrial RFID tag 2104 associated withthe sub-assembly may contain all the history data from the parts thatconstitute it. This may be accomplished through a facility associatedwith the reader 140, reading the data from all parts and subsequentlywriting the data into the sub-assembly's industrial RFID tag 2104, orhaving the sub-assembly industrial RFID tag 2104 communicate directlywith the part's industrial RFID tags 2104. With industrial RFID tags2104 associated with parts, sub-assemblies, assemblies, finishedproducts, and the like, all components used in the manufacturing processmay be tracked and located. In embodiments, the ability to track andlocate any part, sub-assembly, or assembly in the manufacturingfacility, may improve the efficiency of the manufacturing facility.

The tracking and location of parts within the manufacturing facility maybegin with parts being received at the manufacturing facility. Parts maybe received with industrial RFID tags 2104 already attached, or theindustrial RFID tags 2104 may have to be attached when the part isreceived. Whether the industrial RFID tag 2104 is attached to the partitself, or attached to its container, the industrial RFID tag 2104 mayallow for a simple and quick way to perform stocking and vending ofinventory. For instance, the stocking and vending facility may have anarray of readers that covers the entire stockroom area, including thereceiving area and the vending, or outgoing, area. As parts withindustrial RFID tags 2104 are received, the stocking and vendingfacility logs the part in and tracks its location. Similarly, when partscome in with no industrial RFID tag 2104, the part is tracked from thetime an industrial RFID tag 2104 is attached. As parts are placed intostock, their industrial RFID tag 2104 may be always accessible, and thepart's location and history data may be always available. As parts arevended out of stores, the stocking and vending facility may log the partout of stores and onto the manufacturing floor. In this way, thestocking and vending facility may have a continuous log of what isreceived, stored, and vended within inventory. In addition, becauseparts may come with an industrial RFID tag 2104 containing history data,the stocking and vending facility may have access to history informationfor parts in inventory. Further, the stocking and vending facility mayutilize these part histories to create a database that may enable themanufacturing facility immediate access to real-time inventory. Inembodiments, the systems and methods described herein may better enablereal-time inventory control, and may provide easy access to a real-timepart history database.

Warehouse systems 2308 may benefit from the systems and methodsdescribed herein in ways similar to those described above for monitoringfactory inventory, such as the tracking and location of all products inthe warehouse system 2308, a real-time database of stock, automatedaddition of stock at receiving, automated material stocking and returnsystems, automated tracking of vending systems at departure, historyinformation on all stock in the warehouse system 2308, or the like.Material location and tracking systems may be applied at all levels ofwarehouse packaging, such as container-level, pallet-level, case-level,product-level, or the like. In embodiments, the systems and methodsdescribed herein may enable more efficient stock management within thewarehouse system 2308.

In addition, warehouse stock, as well as inventory stock, may have timeexpiration codes or environmental limits that require monitoring.Typically, this monitoring may have been done with a database system.But logging in and out all the information associated with stock,especially with the warehouse system 2308 where there turnover of stockmay be high, can be time consuming and prone to human error. The systemsand methods described herein provide extended memory and functionalitythat may support an automated way to have stock self-report warnings dueto such variables as time expiration, environmental limits, handlinglimits, or the like. Through such extended memory, these variables maybe stored in the industrial RFID tag's 2104 memory. Through suchextended functionality, these variables may be actively compared toexternal references, such as current time provided by the reader 140signal, or sensor 138A data, such as temperature, humidity, shock, orthe like. Periodic interrogations by warehouse system 2308 readers 140may provide the power for the industrial RFID tag 2104 to assess andreport on any conditions that may warrant caution or warning.

As an example, the warehouse system may be storing a perishable foodproduct such as milk. The milk may have perishable limits that cannot beexceeded without loss of the product, such as a sell-buy date code,minimum and maximum temperature extremes, maximum shock to the shippingcontainer, or the like. This information, along with its identificationnumber, may be stored in the milk's industrial RFID tag 2104, and may betransferred to the warehouse system 2308 database when the milk isreceived. The milk may then be stored in the warehouse system for sometime duration before being shipped out. The warehouse system 2308 may bea company separate from the company that produced, packaged, andtransported the milk to the warehouse system 2308 site. It is essentialfor a warehouse system 2303 that handles perishables to prevent theproduct from expiring, and if it does expire, to identify the point inthe supply chain where the product experienced the out of limitparameter. Therefore, the warehouse system 2308 may read theseparameters from the product's industrial RFID tag 2104 upon receivingthe product, for example, to determine whether the milk has expiredprior to receiving. Once the milk is determined to be good, and not tohave exceeded any product parameters, the milk may be stored. Duringstorage, the warehouse system 2308 may monitor the product's parameterlimits within its database. But the database may not be monitoring theproduct itself, and parameters such as temperature and shock may only beaccurately monitored at the product location. For example, the databasemay not be able to detect whether the milk's shipping container wasdropped, or whether local temperature variations within the warehousesystem 2308 caused temperature parameters to be exceeded. Monitoringparameters at the product's location may be the most accurate way toensure that product parameters are not exceeded.

In an embodiment, the systems and methods described herein may providefor monitoring product parameters at the location of the product, andreporting status and warnings to the warehouse system 2308. For example,the bottle of milk with an industrial RFID tag 2104 attached, may becontinuously monitored for time, temperature, shock, or the like.Readers 140 distributed throughout the warehouse system 2308 mayperiodically interrogate the industrial RFID tags 2104 within thewarehouse system 2308. Sensors 138 may be continuously monitoringparameters, and when the industrial RFID tag 2104 is interrogated, theindustrial RFID tag 2104 may then read sensor 138A data and comparetheir values to parameter limits. Sensors may be independently powered,and so the industrial RFID tag 2104 may be reading a data history sincethe sensor's last access by the industrial RFID tag 2104. If conditionswere near or in excess to parameter limits, the industrial RFID tag 2104may report a warning to the warehouse system 2308 to indicate a possibleproblem. The systems and methods described herein may take advantage ofextended memory and/or functionality to perform this self-monitoring andself-reporting. In embodiments, the systems and methods described hereinmay help reduce the loss of product during warehousing, locate where theproduct experienced the out-of-limit condition, track the conditionsunder which the product was warehoused, or the like.

In embodiments, the warehouse system 2308 may have need of navigationsystem to locate products for shipment out of the warehouse system 2308.The systems and methods described herein may provide a way for locatingproduct within the warehouse system 2308. For example, at timeswarehouses or other industry facilities may utilize a forklift forfactory transportation 2310 to help facilitate the storage and retrievalof products. In embodiments, it may be useful for the forklift to have anavigation system that leads the forklift operator to the location ofthe desired product. The initial directions provided by the navigationsystem may be provided though the network of readers 140 throughout thewarehouse system 2308. The forklift may also have its own reader 138. Asthe forklift reader 138 comes into range with the industrial RFID tag2104 of the product, the forklift may be directed to the exact locationof the product, possibly even employing triangulation methods withmultiple readers 140 within the warehouse system 2308. When the forklifthas successfully retrieved the product, the forklift navigation systemmay list all products that are currently being transported by theforklift. This information may then be relayed to the warehouse system2308 database, to transport facilities for departure, to receivingfacilities to indicate space available, or the like. A forkliftembodying certain systems and methods described herein may be automated,that is, not requiring a human operator. Where as the forklift has beenused as an example of how the systems and methods described herein maybe used in product location and transport, other examples, such ashandheld readers, wand readers, winch readers, or the like, may also beutilized. In embodiments, the systems and methods described herein mayprovide a more efficient way to locate products within the warehousesystem 2308.

Other industrial transportation 2310 facilities may include industrialelevator systems, industrial escalator systems, industrial conveyorsystems, cargo terminal systems, or the like. In transporting products,primary concerns may include products being misplaced or mishandled,which may cause loss of time and/or loss of product. The systems andmethods described herein may allow a product associated with anindustrial RFID tag 2104 to be located within a network of reader 140facilities, reporting not only its identification, but its handling andenvironmental history. For example, a series of ten part kits may besent down a conveyor system to an assembly area, but only nine kits arecounted at the end of the conveyor system. Typically this would initiatea search for the missing kit at the sending end, along the conveyor, andat the receiving end of the conveyor system. This would typicallyinvolve personnel, and reduce the efficiency of the assembly facility.With the systems and methods described herein, and in conjunction with aportable reader or network of readers, the part kit may be quicklylocated. In addition, the handling and environmental history for theparts kit may be read to determine if any degradation to componentswithin the kit may have occurred.

The transportation systems 2310 outside the warehouse facility maybenefit from the parameter monitoring capabilities using the systems andmethods described herein in similar ways to warehouse systems 2308, suchas having readers on transport facilities that are able to determine thestate of the product when received, monitor product parameter limitsduring transport, locate products with portable or mobile reader140/navigation systems, or the like. For example, in loading a productonto a truck for transportation to a distribution site, the systems andmethods described herein may be utilized to determine whether productparameter limits have been exceeded prior to loading onto the truck.With all product loaded onto the truck, a reader 140 on the truck maymonitor products with industrial RFID tags 2104, and alert the driver ifparameter limits are being approached or exceeded. When the truckreaches a distribution point, and some product is to be off-loaded,hand-held readers, possibly in conjunction with the truck's reader, maybe utilized to locate specific products. Receiving personnel may accessproduct industrial RFID tag 2104 memory to transfer the status andhistory of the products being off-loaded into a local database. Forinstance, if a product has been dropped or mishandled, sensor 138A datamay indicate this when read from the memory of the industrial RFID tag2104. In embodiments, the systems and methods described herein mayincrease the ability to monitor product handling and environment duringtransportation.

Global factory product transportation 2310 may involve containerization,a system of inter-modal cargo transport using standard ISO containers,also known as isotainers, that can be loaded and sealed intact ontocontainer ships, railroad cars, planes, and trucks. Typically the cargois loaded into containers, mounted on rail or truck, and transported toa container terminal for sea or air transport. The contents of thecontainers are not typically removed from the containers as they areshifted between truck, rail, ship, and air, in transit from source todestination. Given the potentially long durations for global shipment offactory products via containerization, and the great variety ofenvironmental conditions that the products may experience, it may beparamount to maintain a history including time, mode of transport, ownerof transport, environmental conditions during transport, shockenvironments during transport, or the like. The capabilities of thesystems and methods described herein may be ideal for maintainingreliable long-term monitoring of the product's conditions while intransport. A reader 140 network on the various transportation modes maybe utilized for monitoring and/or activation of the product's industrialRFID tag 2104.

Factory transportation 2310 through the system of containerization mayprovide a varied shock environment to the container and associatedcargo. For example, moving containers from one mode of transport toanother, such as from truck-to-train, train-to-dock, dock-to-ship, orthe like, may impart shock to the cargo. Transporting a fragile product,such as glass, may cause breakage as a result of handling. The transportagency may specify maximum instantaneous accelerations due to shock thatare to be taken as acceptable in shipment. In embodiments, these values,along with other specified environmental conditions for transport, maybe stored in the memory of the industrial RFID tag 2104 associated withthe product. The industrial RFID tag 2104 may monitor its associatedsensors 138, and compare sensor 138A values to the stored specifiedmaximums. If the measured values exceed the specified maximums, theindustrial RFID tag 2104 may transmit a status or warning to residentreaders 140, as well as to a running log to be read by the cargo'seventual recipient. In this way, it can be determined quantitativelywhether any breakage was due to poor packaging or to excessive shockduring transport. Industrial RFID tags 2104 may also communicate withlocal readers 140 or with other industrial RFID tags 2104 to attempt toreport or cross correlate its readings with the readings of otherindustrial RFID tags 2104. In embodiments, the industrial RFID tag 2104reporting the anomalous reading may read and record data provided fromthe network of readers 140, or from other local industrial RFID tags2104.

A number of other parameters may be specified by the transport agencywhere certain limits are not to be exceeded. For example, in thetransport of perishable goods or livestock, certain temperature maximaor minima must not be exceeded. Industrial RFID 2104 tags incorporatedin the packaging or containers for perishable goods, or incorporated inthe pens or shipping crates for livestock, may indicate exposuretemperatures. Such tags 2104 may also be attached to individual animalsfor livestock shipments. It can be determined by reading the data on theindustrial RFID 2104 tags whether temperature tolerances have beenexceeded during the shipment, to the potential detriment of the goods orlivestock. In addition to large-scale or bulk shipments, industrial RFID2104 tags may be affixed to or imbedded into unique items of livestock,such as performance animals (e.g., circus animals, rodeo animals, andthe like), laboratory animals, or pets. Because such specializedshipments may have detailed requirements for their transportation, andnarrow tolerance ranges, industrial RFID 2104 tags may be used tocollect data regarding transportation conditions to determine whether,for example, contractually-determined transportation requirements havebeen met.

In addition to industrial RFID tags 2104 on the products or theirpackaging, there may be industrial RFID tags 2104 on the shippingcontainer itself, providing a unique identification number for eachcontainer. Additionally, the container's industrial RFID tag 2104 maycollect the information resident on product level industrial RFID tags2104 internal to the container. Since the container's industrial RFIDtags 2104 may be external, and the container may be metallic, there maybe an interface between the industrial RFID tags 2104 on productsinternal to the container, and the industrial RFID tag 2104 for thecontainer, mounted on the container. In this way, external readers 140may more easily read the contents of the container. In embodiments, thecontainer's industrial RFID tag 2104 may be mounted on the externalsurface of the container, and as such, may be more exposed to theoutside elements and to physical contact with container handlingequipment and other containers. As a result, damage to the industrialRFID tag 2104 may be more likely, and may require greater reliabilitythan is typical for RFID tags. The systems and methods described hereinmay have significant redundancy capabilities due to the multiple RFnetwork node 104 configuration of the tag 102. In embodiments, thesystems and methods described herein may provide significantly greaterredundancy than typical RFID tags, and may be an advantageous solutionto the requirements of the container's industrial RFID tag 2104.

In industrial applications, quality control is involved in ensuringproducts are produced to meet or exceed customer requirements. Thesystems and methods described herein may enable the tracking and loggingof quality control history for a product. This history may begin at theparts level, including information such as lot, date, part testing atsource, or the like. The quality testing results and information forparts may then be aggregated into the sub-assembly level, and then tothe assembly, and finished product level. In this way, informationrecorded on the industrial RFID tags 2104 of a lower assembly may becollected and transferred to the industrial RFID tag 2104 of a higherassembly, which may allow all information associated with a finishedproduct to build as an integral part of the assembled product. Inembodiments, the systems and methods described herein may eliminate theneed for an external file to keep track of quality control results andlogs. This may allow the quality control information to be networked viareaders 140, and/or accessed by hand-held readers by quality controlpersonnel. In embodiments, the systems and methods described herein maylead to more efficient quality management, and greater reliability inquality control record keeping.

Aspects of the systems and methods described herein may be used in manydifferent consumer markets where material, parts, products, processes,and the like may benefit from history tracking, movement tracking,identification, data recording, or other recording information on aconsumer RFID tag 2108. Referring to FIG. 24, consumer market examplesmay include government issued personal identification 2402, personalidentification card 2404, general personal identification systems 2408,consumer product systems 2410, home security 2412, home automationsystems 2414, residential plant control and access, or the like.

The consumer RFID tag 2108 may be connected to a network where thenetwork connection may be a wireless connection, a wired connection, orthe like. The network to which the consumer RFID tag 2108 maycommunicate may be a LAN, a WAN, a peer-to-peer network, an intranet, anInternet, or the like. The network connection may be use the gatewayfacility 138C discussed in FIG. 11.

An aspect of the systems and methods described herein may relate toassociating the RFID tag with a government identification and storingand communicating consumer RFID tag 2108 information related to agovernment identification 2402.

In an embodiment, the government identification 2402 may be a passport.The owner of the passport may be tracked within a passport zone. Thegovernment identification may provide automatic identification at apassport checkpoint.

In an embodiment, the government identification 2402 may be a visa. Theowner of the visa may be tracked within a visa zone. The governmentidentification 2402 may provide automatic identification at a visacheckpoint.

Additionally, the government identification may be a driver's license, apublic safety personnel identification, a government employeeidentification, or the like.

In an embodiment, the government identification 2402 may provideautomatic access to a location, manual access to a location, or thelike.

In an embodiment, the government identification 2402 information may bea user name, user address, user personal characteristics, a user placeof work, a user rank, or the like.

In an embodiment, the government identification 2204 may track a user'singress and egress to a facility.

An aspect of the systems and methods described herein may be associatingthe consumer RFID tag 2108 with a personal identification 2404 andstoring and communicating consumer RFID tag 2108 information related toa personal identification 2404.

In an embodiment, the personal identification 2404 may be related to acredit card. Items may be automatically purchased with the credit cardusing a reader 140. In an embodiment, the credit card may provideautomatic identification of a user.

In an embodiment, the personal identification 2404 may be related to anATM card. Items may be automatically purchased with the ATM card using areader 140. In an embodiment, the ATM card may provide automaticidentification of a user.

In an embodiment, the personal identification 2404 may be related to abankbook.

Aspects of the systems and methods described herein may be associatingthe RFID tag with a product and storing and communicating consumer RFIDtag 2108 information related to a product warranty. In an embodiment,the warranty information may be a product part number, a product serialnumber, a date of purchase, a date the warranty expires, a warrantycontract, an owner's identification, a return date, a return controlnumber, or the like.

An aspect of the systems and methods described herein may be associatingthe consumer RFID tag 2108 with a home security system 2412 and storingand communicating the consumer RFID tag 2108 information related to homesecurity 2412. Home security may be intrusion detection, fire detection,water detection, smoke detection, or the like.

In an embodiment, the home security system 2412 information may berelated to a status of home locks such as when the home lock is lockedor unlocked.

In an embodiment, the home security system 2412 information may berelated to a personal identification facility where the personalidentification facility may contain home egress and ingress information.In an embodiment, the home information may automatically lock and unlockdoors. In an embodiment, the home information may manually lock andunlock doors. In an embodiment, the home information may automaticallylock and unlock windows. In an embodiment, the home information maymanually lock and unlock windows.

In an embodiment, the home information may automatically secure a homezone when leaving the zone. The home information may automaticallyadjust the security when the zone is reentered.

An aspect of the systems and methods described herein may be associatingthe consumer RFID tag 2108 with a home automation system 2414 andstoring and communicating consumer RFID tag 2108 information related tohome automation 2414. Home automation may be turning lights on and off,dimming lights, turning entertainment systems on and off, adjusting anenvironmental control within a zone, or the like.

In an embodiment, the home automation 2414 information may include auser's personal settings. The user's personal setting may be activatedwhen entering a zone of a home. In an embodiment, the home automationinformation may be modifiable. The information may be modified based ona last setting of the home automation system, modified by a user, or thelike.

Aspects of the systems and methods described herein may be used in manydifferent government markets where material, parts, products, processes,and the like may benefit from history tracking, movement tracking,identification, data recording, or other recording information on agovernment RFID tag 2110. Referring to FIG. 25, government marketexamples may include public safety 2502, public infrastructure 2504,public transit systems 2508, transportation systems 2510, customssecurity systems 2512, border security systems 2514, passport controlsystems 2518, and visa control systems.

The government RFID tag 2110 may be connected to a network where thenetwork connection may be a wireless connection, a wired connection, orthe like. The network to which the government RFID tag 2110 maycommunicate with a LAN, a WAN, a peer-to-peer network, an intranet, anInternet, or the like. The network connection may be use the gatewayfacility 138C discussed in FIG. 11.

An aspect of the systems and methods described herein may be associatingthe government RFID tag 2110 with a security device and storing andcommunicating government RFID tag 2110 information related to publicsafety 2502.

In an embodiment, the security device may include information for acorrectional facility. The correctional facility device may provideingress and egress tracking. The correctional facility device mayprovide location information for the security device. In an embodiment,the correctional facility device may be associated with a person, withan object, or the like.

In an embodiment, the security device may include information for acourthouse. The courthouse device may provide ingress and egresstracking. The courthouse device may provide the location information ofthe security device. The courthouse device may be associated with aperson, with an object, or the like.

In an embodiment, the security device may be associated with a GPSsystem. The security device may provide a prisoner location, a personnellocation, or the like. The security device may provide ingress andegress information from a zone.

An aspect of the systems and methods described herein may includeassociating the RFID tag with a vehicle infrastructure device andstoring and communicating government RFID tag 2110 information relatedto public infrastructure 2504. The public infrastructure may includetransportation control such as traffic control, bridge access andcontrol, tunnel access and control, and the safety of vehicles operationon the public infrastructure.

In an embodiment, the transportation control may be traffic flowcontrol. The information may be used to control the coordination of atleast one street traffic light to control the flow of traffic through acity, town, or the like.

In an embodiment, the transportation control may be bridge flow controlwhere the information may be used to control the number of vehicles onthe bridge. The information may be used to control access to the bridge.

In an embodiment, the transportation control may be tunnel flow controlwhere the information may be used to control the number of vehicles inthe tunnel. The information may be used to control access to the tunnel.

In an embodiment, the transportation control may provide automaticpayment of tolls. The information may be a vehicle identification, avehicle owner, a history of toll access, a last safety inspection on avehicle, or the like. In an embodiment, the safety inspectioninformation may indicate a pass and fail of the safety inspection forthe vehicle. The vehicle may be denied access if the vehicle failedinspection.

An aspect of the systems and methods described herein may be associatingthe RFID tag with a personal infrastructure device and storing andcommunicating government RFID tag 2110 information related to publictransit systems 2504 transportation control. In an embodiment, thepersonal infrastructure device may be a card, a loyalty card, a creditcard, a transportation system device, or the like.

In an embodiment, the personal infrastructure device may provideautomatic ingress and egress control to a public transportation system.The public transportation system may be a bus, a train, a subway, andthe like. In an embodiment, the personal infrastructure device may storeuser identification information, an egress and ingress history, a valueof the personal infrastructure device, or the like. The personalinfrastructure device value may be automatically added, deducted, or thelike.

In an embodiment, the personal infrastructure device may store wantedpersons information for the owner of the personal infrastructure device.The wanted owner ingress and egress may be tracked during ingress andegress from public transportation. The wanted owner may be denied accessto a public transportation system.

In an embodiment, the personal infrastructure device may providelocation information within a public transportation station.

An aspect of the systems and methods described herein may be associatingthe government RFID tag 2110 with a customs security device and storingand communicating government RFID tag 2110 information related tocustoms control 2512.

In an embodiment, the customs device may be associated with baggage tostore information about the baggage. The baggage information may containa declaration of the baggage contents, baggage owner identification, afinal destination, a starting location, at least one interimdestination, or the like. In an embodiment, the baggage may be trackedwhile the baggage is within the customs area.

An aspect of the systems and methods described herein may be associatingthe government RFID tag 2110 with a border security device and storingand communicating government RFID tag 2110 information related to bordercontrol 2514.

In an embodiment, the border security device may be used as a coverttagging device for tracking objects or people as they cross borders. Inan embodiment, the covert information may be a border crossing name, aborder crossing time, an identification of the user crossing the border,or the like. In an embodiment, the border security device may be trackedeach time the border security device is in a border crossing area.

In an embodiment, the border security device may be tracked when theborder security device is in-custody of a border crossing for trackingobjects and people when in the in-custody area of border security. In anembodiment, information on the border security device may containinformation on ingress and egress from the in-custody area, locationinformation for within the in-custody area, user information for theborder security device, or the like.

Aspects of the systems and methods described herein may be used in manydifferent agriculture markets where material, parts, products,processes, and the like may benefit from history tracking, movementtracking, identification, data recording, or other recording informationon an agriculture RFID tag 2112. Referring to FIG. 26, agriculturemarket examples may include transportation 2602, inventory control 2604,time a product is on a shelf 2608, freshness tracking 2610, and thelike.

The agriculture RFID tag 2112 may be connected to a network where thenetwork connection may be a wireless connection, a wired connection, orthe like. The network to which the agriculture RFID tag 2112 maycommunicate with a LAN, a WAN, a peer-to-peer network, an intranet, anInternet, or the like. The network connection may be use the gatewayfacility 138C discussed in FIG. 11.

An aspect of the systems and methods described herein may be associatingthe agriculture RFID tag 2112 with an agriculture product and storingand communicating agriculture RFID tag 2112 information related to theagriculture product. In an embodiment, the agriculture RFID tag 2112 maybe connected to a sensor for measurement of environmental conditions ofvarious agriculture products. In an embodiment, the sensor may be atemperature sensor, a humidity sensor, an acceleration sensor, or thelike.

In an embodiment, the environmental conditions of the agricultureproduct transportation 2602 may be recorded such as temperature,humidity, handling of the agriculture product (e.g. dropping),transportation time, or the like.

In an embodiment, the agriculture information may be related toinventory control 2604. In an embodiment, the information may be theamount of agriculture product within a distribution system, a warehouse,a store, or the like. In an embodiment, the agriculture informationrelated to inventory control may be aggregated remotely from theagriculture product at the plurality of locations within the inventorycontrol 2604 system.

In an embodiment, the agriculture information may be related to thefreshness of the agriculture product. In an embodiment, the agricultureinformation may be the time since the agriculture product has beenharvested, an environmental condition of the agriculture product sinceharvesting, or the like for determination of the agriculture freshness2610. In an embodiment, sensors may record the environmental conditionsof the agriculture product; the information may be tracked remotely froma location of the agriculture product.

Aspects of the systems and methods described herein may be used in manydifferent markets where material, parts, products, processes, and thelike may benefit from history tacking, movement tracking,identification, data recording, or other recording information.Referring to FIG. 27, a market example may be military applications,where information may be for tracking munitions inventory, tracking foodinventory, food expiration dates, tracking personnel, tracking battlemovements, supply material tracking, automatic identification,maintenance, casualty tracking, and the like. The military, and theDepartment of Defense (DoD) in general, is a large and complexorganization that has requirements to track large supply chains, providesecurity for locations and personnel, track movements of personnel andvehicles within a military facility, and the like.

The military may benefit from the use of automatic tracking systems thatmay be provided by the systems and methods disclosed herein. The multiRF network node 104 RFID tag 102 may provide increased memory foradditional storage of information related to the type of product towhich the RFID tag 102 is attached, information related to the movementof the product, information related to the personnel in possession ofthe product, and the like. The increased memory may be implemented asredundant memory to provide a more robust RFID tag 102 for situationswhere the product may be in a harsh environment. The RFID tag 102 asdescribed herein may also provide functional redundancy where the RFIDtag 102 may be able to incur some damage and continue to provide normalfunctions.

Additionally, the RFID tag 102's capability of multiple frequencies andmultiple antennas may allow the military to transmit and receiveinformation from the RFID tag 102 using a number of differentfrequencies. Certain parts of the RFID tag 102 memory may only beaccessed by certain frequencies and/or encryptions. These capabilitiesmay provide secure storage of information for many different productsfor which the military has responsibility.

Referring to FIG. 27, the military RFID tag 2114 may be applicable tomunitions tracking 2702, food 2704, personnel tracking 2708, battlemovement 2710, material tracking 2712, automatic identification 2714,vehicle maintenance 2718, and casualty tracking 2720. It should beunderstood by someone knowledgeable in the art that the military RFIDtag 2114 may have other applications in the military and the listedapplications is not intended to be limiting.

As may be readily understood, the military has a significant amount ofmunitions to store, transport, track, disperse, and the like, rangingfrom small caliper to larger munitions. The military may be interestedin tracking the amount of munitions available, the type of munitionsavailable, the distribution of the munitions, the munitions available toa unit, and the like. The military RFID tag 2114 may be attached to themunitions, may be attached to the munitions container, or the like. Inan embodiment, the increased memory of the military RFID tag 2114 of thesystems and methods described herein may allow for increased amounts ofinformation to be stored about the munitions such as the type ofmunitions, the amount of munitions within the storage container, the ageof the munitions, the location of the munitions, part numbers, serialnumbers, and the like. Depending on the security requirements, some orall of the information may be stored with a password, with encryption,with a combination of password and encryption, or the like.

Using the information stored on the military RFID tag 2114, the militarywarehouses and stores could utilize smart shelf inventory for munitions.Using the military RFID tag 2114 associated to the munitions and atleast one reader 140 within a warehouse, the munitions may beinventoried rapidly. The read or series of reads may be able todetermine the amount of all the munitions within the warehouse, theamount of certain munitions within a warehouse, the age of themunitions, and the like. This type of smart shelf inventory may be usedin large base warehouses and smaller field munitions stores to allow forrapid munitions determination. With this RFID tag 102 technology, theinventory of munitions in many widely separated warehouses may bedetermined within a short period of time. For example, an entire Commandmay inventory the munitions in a plurality of munitions warehouses byreading the military RFID tags 2114 associated with the munitions. Themilitary RFID tag 2114 readers 140 may be associated with a network as,described herein, to allow a remote site to initiate a read ofinformation and receive information for the munitions inventory. Themunitions information may then be aggregated for the Command to providethe overall munitions readiness of the Command. The aggregation ofmunitions information may allow the Command to determine the number andtype of munitions that are stored in all of the units within theCommand.

The military RFID tag 2114 may also be used to track the movement ofmunitions into and out of the munitions warehouse. For example, as newmunitions are stored in the warehouse, the military RFID tag 2114 may beread and added to the inventory of the warehouse. Similarly, whenmunitions are removed from the warehouse, the munitions information maybe removed from the warehouse. Additionally, the personnel removing themunitions may also have a military RFID tag 2114 that may identify thepersonnel. As the munitions are checked out of the warehouse, thepersonnel identification may also be read to create a history record ofthe munitions movements and the personnel that moved the munitions.Furthermore, when certain munitions are added to the inventory ofanother warehouse (e.g. a field munitions storage), the munitionsmilitary RFID tag 2114 may be read and the munitions information addedto the other warehouse.

During the movements of the munitions from one warehouse to another, themunitions information may be read by a reader 140 and stored to thenetwork 152 allowing for aggregation, searching, sorting, or the like ofthe munitions information from remote locations. Additionally, as thereader 140 reads the movement information, the movement information maybe stored onto the munitions military RFID tag 2114. Therefore themunitions military RFID tag 2114 may contain the entire distributionhistory that may be read by a reader 140 within a warehouse, a portablereader, or the like.

Using the smart self inventory within the warehouse and the tracking ofmunitions being added and removed from the warehouse, automaticmunitions ordering may be implemented based on preset inventory levelrequirements. For example, when munitions are removed from a centralwarehouse and dispersed to smaller field warehouses, the automaticinventory levels determined by the military RFID tag 2114 informationmay initiate an order for replacement munitions.

As an additional aspect of the munitions inventory, the munitionsmilitary RFID tag 2114 may be read as it is moved within the munitionsdistribution system. There may be checkpoints along the distributionsystem such as at airports, at rail stations, at trucking stations, onloading docks, on transports (e.g. aircraft, trains, trucks), and thelike. In this manner, the munitions may be tracked from the startingpoint of the distribution system until it is received at the finaldestination. Using readers 140 that are associated with the network 152,a remote site may be able track the munitions throughout the entiredistribution system. In an embodiment, the remote site may be providedwith an alert when the munitions do not move within the distributionsystem in a predictable manner.

The DoD may require a significant amount of food 2704 to supply all themilitary personnel within its responsibility. The military food 2704,similar to retail or commercial food, may require inventory tracking,distribution tracking, shelf life determination, and the like. MilitaryRFID tags 2114 of the systems and methods described herein may be usedto track inventories, distribution, freshness, and the like by storinginformation about the product to which it is associated. The increasedmemory in a multi RF network node 104 military RFID tag 2114 may allowfor storing information about the type of food 2704, the amount of food2704, the original supplier of the food 2704, the time on the shelf, theenvironment in which the food 2704 has been stored, and the like. Thisinformation may be stored in public memory, private memory, encryptedmemory, or the like. The increased memory of the military RFID tag 2114of the systems and methods described herein may allow for redundantmemory for foods that may be stored in harsh environments such as hotdry environments, wet environments, cold environments, and the like. Theredundant memory may allow for damage to the military RFID tag 2114 thatstill provide memory storage and functionality.

Using the information stored on the military RFID tag 2114, the militarywarehouses and stores could utilize smart shelf inventory for food.Using the military RFID tag 2114 associated to the food and at least onereader 140 within a warehouse, the food may be inventoried rapidly. Theread or series of reads may be able to determine the amount of all thefood within the warehouse, the amount of certain food within awarehouse, the age of the food, expiration dates of the food, and thelike. This type of smart shelf inventory may be used in large basewarehouses and smaller field stores to allow for rapid food supplydetermination. With this RFID tag 102 technology, the inventory of foodin many widely separated warehouses may be determined within a shortperiod of time. For example, an entire Command may inventory the food ina plurality of food warehouses by reading the military RFID tags 2114associated with the food. The military RFID tag 2114 readers 140 may beassociated with a network as, described herein, to allow a remote siteto initiate a read of information and receive information for the foodinventory. The munitions information may then be aggregated for theCommand to provide the overall food readiness of the Command. Theaggregation of food information may allow the Command to determine theamount and type of food that are stored in all of the units within theCommand.

The military RFID tag 2114 may also be used to track the movement offood into and out of the food warehouse. For example, as new food isstored in the warehouse, the military RFID tag 2114 may be read andadded to the inventory of the warehouse. Similarly, when food is removedfrom the warehouse, the food information may be removed from thewarehouse. Additionally, the personnel removing the food may also have amilitary RFID tag 2114 that may identify the personnel. As the food ischecked out of the warehouse, the personnel identification may also beread to create a history record of the food movements and the personnelthat moved the food. Furthermore, when the food is added to theinventory of another warehouse (e.g. a field food storage), the foodmilitary RFID tag 2114 may be read and the food information added to theother warehouse.

During the movements of the food from one warehouse to another, the foodinformation may be read by a reader 140 and stored to the network 152allowing for aggregation, searching, sorting, or the like of the foodinformation from remote locations. Additionally, as the reader 140 readsthe movement information, the movement information may be stored ontothe food military RFID tag 2114. Therefore the food military RFID tag2114 may contain the entire distribution history that may be read by areader 140 within a warehouse, a portable reader, or the like.

Using the smart self inventory within the warehouse and the tracking offood being added and removed from the warehouse, automatic food orderingmay be implemented based on preset inventory level requirements. Forexample, when food is removed from a central warehouse and dispersed tosmaller field warehouses, the automatic inventory levels determined bythe military RFID tag 2114 information may initiate an order forreplacement food.

As an additional aspect of the food inventory, the food military RFIDtag 2114 may be read as it is moved within the food distribution system.There may be checkpoints along the distribution system such as atairports, at rail stations, at trucking stations, on loading docks, ontransports (e.g. aircraft, trains, trucks), and the like. In thismanner, the food may be tracked from the starting point of thedistribution system until it is received at the final destination. Usingreaders 140 that are associated with the network 152, a remote site maybe able track the food throughout the entire distribution system. In anembodiment, the remote site may be provided with an alert when the fooddoes not move within the distribution system in a predictable manner.

In another aspect of inventory and movement of food associated withmilitary RFID tags 2114 may be the availability of food within the DoD.For example, by reading the military RFID tag 2114 information withinfood warehouses, the DoD may be able to aggregate a “snap shot” of foodinformation within the warehouse and distribution system. The snap shotmay provide the ability to determine the amount and type of food thatmay be stored in which warehouses and/or within the distribution system.For example, if one branch of the DoD requires a certain type of mealsready to eat (MRE), the DoD may be able to determine the supply andlocation of the required MRE and determine if the MRE can be distributedto the requiring branch or if additional MREs need to be ordered.

As described herein, the food military RFID tag 2114 may be associatedwith at least one sensor 138A, the sensor 138A may measure temperature,humidity, acceleration, and the like and provide the measuredinformation to the military RFID tag 2114. In an embodiment, during aread of the military RFID tag 2114, the military RFID tag 2114 may readthe information from the sensor 138A. The sensor 138A information may bestored on the military RFID tag 2114, transmitted to the reader 140,stored on the military RFID tag 2114 and transmitted to the reader 140,or the like. The sensor information may provide a storage history of thefood and may be used to indicate the shelf life of the food.

For example, perishable foods such as fruits and vegetables may have alimited shelf life if stored at elevated temperatures. The military RFIDtag 2114 associated with the food may have a temperature sensor 138Athat may provide a temperature history of the food that may be used todetermine the freshness of the food. In this manner, the shelf life ofmilitary food may be determined from a remote location by requesting aread of the food military RFID tag 2114. In an embodiment, the foodsself life may be calculated on the military RFID tag 2114, calculated ata remote location after the read, calculated by both the military RFIDtag 2114 and the remote location, or the like. In an embodiment, thesensor 138A may be self powered and able to read temperaturescontinuously; the sensor 138A may be able to store some or all of thetemperature information. When the military RFID tag 2114 is read, themilitary RFID tag 2114 may read the instantaneous temperatureinformation, the temperature history information, or a combination ofthe instantaneous and historical information.

In another example, the environment in which it is stored may affecteven long life, or non-perishable foods. The MRE may be considered along shelf life product but may be affected by very hot temperatures orvery wet environments. In an embodiment, the MRE may have a militaryRFID tag 2114 that tracks the temperature, humidity, and the like usingsensors 138. The MRE military RFID tag 2114 may be able to read thesensors 138 and calculate the affect the environment may have on theMRE. A portable reader 140 may be used to read the expiration date ofthe MRE as it is being distributed to verify the freshness of the MRE.For example, if the MRE is stored in the desert for a long period oftime, the shelf life may be reduced. The sensor on the military RFID tag2114 may continuously read the environment and store the environmentinformation to the MRE military RFID tag 2114 during each read. Witheach read, the military RFID tag may calculate the new expiration dateof the MRE. The new expiration date may be read at the distributionpoint before being issued to the military personnel.

The military RFID tag 2114 may be associated with militaryidentification and may store and communicate military RFID tag 2114information related to the military tracking 2708. The military RFID tag2114 may be connected to a network that may be a wireless connection, awired connection, or the like. The network may be a LAN, a WAN, apeer-to-peer network, an intranet, an Internet, or the like. The networkconnection may allow the military RFID tag 2114 to transmit informationrelated to personnel identification to a military network for tracking2708, aggregation, reporting, or the like.

The military information may be related to military security where theinformation may provide the tracking 2708 of military personnel. Themilitary information may be the location of military personnel within acamp, within a military building, or the like. The military personnellocation may be automatically recorded on the military RFID tag 2114 ata checkpoint, at a building, or the like. For example, the militarypersonnel location may be tracked 2708 within a base. The militarypersonnel ingress and egress may be recorded on the military RFID tag2114 that may be carried by the military personnel. The militarypersonnel location may be tracked 2708 at a checkpoint where themilitary personnel ingress and egress are recorded on the military RFIDtag 2708.

The military RFID tag 2114 may be associated with a military vehicle andmay store and communicate military RFID tag 2114 information related tothe military vehicle tracking 2712. The military RFID tag 2114 may beconnected to a network that may be a wireless connection, a wiredconnection, or the like. The network may be a LAN, a WAN, a peer-to-peernetwork, an intranet, an Internet, or the like. The network connectionmay allow the military RFID tag 2114 to transmit information related tovehicle identification to a military network for vehicle tracking 2712,aggregation, reporting, or the like.

The information may be related to a type of the military vehicle. Theinformation may be related to a location of the military vehicle; themilitary vehicle location may be tracked 2712 within a base, at acheckpoint, or the like. The information may include information aboutthe driver of the military vehicle, the contents of the militaryvehicle, and the like.

The military vehicle information may be related to maintenance 2718 ofthe military vehicle. The military vehicle maintenance 2718 informationmay be a type of vehicle, a make of the vehicle, an owner of thevehicle, a last maintenance date, a last maintenance type performed, anext maintenance date, a next type of maintenance required, amaintenance history of the vehicle, or the like. The military vehiclemaintenance information may be read while the vehicle is within amaintenance facility, at a checkpoint, within a base, within a camp,while the vehicle is moving, while the vehicle is stationary, or thelike to determine if the military vehicle is in need of maintenance2718.

The military RFID tag 2114 may communicate with a vehicle communicationnetwork to receive maintenance information from the military vehicle.For example the received maintenance 2718 information may be lubricantinformation, a fault indicator, a tire pressure, a part identificationassociated with the received maintenance information, or the like.

The military RFID tag 2114 may be associated with military personnel andstore and communicate military RFID tag 2114 information related tomilitary personnel casualty 2720 information. The military RFID tag 2114may be connected to a network that may be a wireless connection, a wiredconnection, or the like. The network may be a LAN, a WAN, a peer-to-peernetwork, an intranet, an Internet, or the like. The network connectionmay allow the military RFID tag 2114 to transmit information related tomilitary casualty tracking 2720 to a military network for rapididentification of information related to the medical history of themilitary personnel.

The casualty tracking 2720 information may relate to the militarypersonnel information that may include a personal identification, ablood type, a military unit, a religious affiliation, allergyinformation, a medical history, or the like. In an embodiment, as themilitary personnel are treated, new medical history may be written tothe casualty tracking 2720 information on the military RFID tag 2114.The personnel information may include location history information ofthe military personnel that may aid in the diagnosis of the militarypersonnel, the location history may include the last movements of themilitary personnel prior to any injury. The RFID tag may provide anautomatic identification of the military casualty information, or theinformation may be read manually using a portable reader 140.

Referring to FIG. 28, a market example may be the medical field, whereinformation may be tracked for monitoring inventories of drugs, medicalproducts and the like within health care facilities, for tracking thedistribution and/or maintenance of medical products, for monitoring thedeployment and status of medical devices, for tracking the progress ofpatients within diagnostic or therapeutic protocols, for providingsecurity within health care facilities, for allocating materialresources or personnel within a health care facility or system, and thelike.

The medical industry presently is a diverse one, with a number of needsfor information tracking. Medical supplies, including devices andpharmaceutical products, are distributed from manufacturer through adistribution chain to end-user. Being able to track a product's statusand location is crucial in the event of a recall, or if resourceallocation becomes problematic, as in times of widespread health careemergencies. It is advantageous, therefore, to be able to follow ashipment unit, for example to locate it for recall, to match scarcesupplies with demands, and the like.

Moreover, while the medical industry may presently collect and storeinformation on hardcopy or internal data stores, the hardcopy or datastores may not follow a pharmaceutical product, a device component or amedical system throughout the life cycle, so that it is difficult toverify the history of the product or component at the point of use. Formedical devices in particular, the life cycle may be prolonged and maytake place under variable conditions where a durable recording devicewith memory capabilities to maintain the life cycle information would bedesirable. This is of particular importance for medical applications,where component failure may have catastrophic implications for patientcare.

Furthermore, as patient care becomes more complex, it may be desirableto permit tracking an individual patient as he or she moves through adiagnostic or therapeutic treatment protocol. A tracking system maypermit data to be gathered at a central location about patient status togive care providers a unified view of the progress that a patient hasmade in accomplishing the steps of a treatment plan. For example, apatient's progress can be monitored as he obtains each of a series ofdiagnostic tests, so that the care provider can be sure that allnecessary information has been obtained and is obtained in the propersequence. The tracking information may be part of an electronic medicalrecord that the patient carries from test site to test site, or it maybe imbedded in an electronic hospital bracelet, or the like, so that thepatient's progress through a sequence of tests may be determined byinterrogating the electronic medical record or electronic hospitalbracelet.

In addition, tracking information can monitor the physical location of apatient or a hospital employee. This can answer staff questions aboutwhere a patient may be within the hospital, or where a particularservice provider may be. Tracking information may also be incorporatedinto a larger-scale surveillance system, so that the location ofcritical personnel within the facility may be determined, for example incase of an emergency. Information about patients or personnel may becarried on an electronic hospital bracelet or an electronic employee IDcard or the like. Such information may be combined with credentials thatallow or forbid access to certain areas of the hospital. An electronicemployee ID card, for example, may permit a pharmacist to enter apharmacy storage room but may prevent an EKG technician from enteringthe same area. Tracking information may also identify which employeesenter which areas, and how many times. Temporary access cards may allownon-employees such as visitors or vendors to enter certain areas, whilebarring them from others. Such information may enhance security in ahealth care facility, or may identify potential security risks. On asystem-wide scale, such information may assist in locating medical andancillary personnel, for example during emergencies.

With reference to FIG. 28, a medical RFID tag 2118 may be used forinstrument and inventory tracking 2802. The RFID tag 2118 may be affixedto medical equipment or instruments to permit monitoring their status.Life cycle information may be recorded for an apparatus or a componentthereof, including such information as when a component was produced,when the component was maintained, when the component is in service,amount of time in service, number of duty cycles, quality checks,information about of the enterprise providing the component or service,and the like. The information may relate to safety, componenttraceability, service tracking, maintenance, life cycle management,quality, part identification and the like.

In an embodiment, safety information borne on the medical RFID tag 2118may be related to electrical grounding, physical integrity, properfitting of components, sterility, indications and contraindications foruse, and the like. Safety information may be stored on the medical RFID2118 to document safety testing, maintenance schedules, or updates. Inan embodiment, using medical RFID tags 2118, each component may besafety checked before a medical instrument is used, or at regularintervals, or after a set number of uses, or the like, to verify theconformity of the component or set of components to safety protocols.The medical RFID tag 2118 may contain the memory requirements to storeall the safety requirement of the component for the life cycle of thecomponent.

In an embodiment, the medical RFID tag 2118 may be related to componenttraceability. Traceability information permits a component to be trackedthroughout its lifecycle, allowing monitoring of the repair history,component utilization, component malfunctions, and the like.Traceability information may also permit the component to be locatedphysically in the event of a component recall. Tracking a componentwithin an assembly of components may permit evaluation of eachindividual element of a larger unit, so that potential problems may beanticipated and pinpointed. During the life cycle of a component manyactions such as repairs, component upgrades, reassemblies, or the likemay be performed on the component or assembly of components. The medicalRFID tag 2118 may record information once the action has been completed,providing a history of the actions performed on the component.

In embodiments, the information recorded on a medical RFID tag 2118 mayprovide for traceability of the actions back to a time, an enterprise, arepair, an assembly, or the like if there is a question of thecomponent's safety or efficacy. For example, a particular instrument mayrequire certain maintenance to preserve its safe functionality. As anexample, an anesthesia machine for delivering inhalable anesthetics mayrequire routine maintenance and inspection of a number of its parts,including supply hoses, valves, fittings, waste gas scavengers,vaporizers, carbon dioxide absorbers and the like. A medical RFID tag2118 may document proper maintenance and/or calibration of each crucialcomponent. As another example, a medical RFID tag 2118 may document thata surgical instrument has undergone proper cleaning and sterilization.

In an embodiment, service tracking may be recorded on the medical RFIDtag 2118 to track the actual usage information of a component, such asthe number of uses for a particular component, the patients for whom thecomponent was used, the service for the component or the like. Somemedical components may have requirements for inspections based on thenumber of patients or patient/hours for which the component has beenused. In an embodiment, the medical RFID tag 2118 may be associated witha sensor to record parameters that may be indicative of a particularuse, such as temperature, pressure, component stress, chemicalcomposition, or the like. Using the sensor, the medical RFID tag 2118may automatically record the characteristics to which a particularcomponent is exposed.

In an embodiment, component maintenance may be recorded on the medicalRFID tag 2118 to track maintenance information about the component suchas the type of repair, the repair technician, the repair dates, therepair enterprise, or the like. In an embodiment, as the componentundergoes has maintenance (e.g. repair, upgrade), the maintenanceinformation may be recorded to the medical RFID tag 2118 to provide amaintenance history of the component. In an embodiment, the maintenancehistory may be read from the medical RFID tag 2118 any time during thecomponent's life cycle. For example, there may be a question of the typeof maintenance performed on a class of components and an enterprise maybe able to query all of the pertinent medical RFID tags 2118 todetermine if the components have undergone proper maintenance. Thiscapability may provide the enterprise a rapid method of componentverification to quickly resolve a question of device safety.

In an embodiment, information may be recorded on the medical RFID tag2118 to track quality related information such as inspection dates,patient use tracking, component configuration, material information,supplier information, or the like. This information may be used in thequality confirmation of a component, used in defect root cause analysis,verification of a proper assembly, comparing the components actual lifecycle information with manufacturer requirements, or the like. In anembodiment, quality control personnel may be able to read the componentquality information for a medical instrument or piece of equipmentbefore its use in a patient, to verify that all of the components withappropriate medical RFID tags 2118 are properly maintained and/orproperly functioning. Additionally, a health care facility may be ableto perform a rapid quality check of all their equipment bearing aparticular component in response to a supplier notification, FDAnotification, risk management alert, or the like by reading all therelevant medical RFID tags 2118.

In embodiments, medical RFID tags 2118 may provide information about thephysical location of equipment and supplies within a facility. A medicalRFID tag 2118 may transmit a signal indicating the position of theequipment within the facility, indicating its availability for use, andthe like. Such information may assist a facility manager in determiningwhat resources are available (e.g., how many unused ventilators are onhand) and where the resources may be located at any particular time(e.g., where the ventilators may be found in the hospital). In addition,the medical RFID tag 2118 may allow components within the facility to bereadily located, for example if routine maintenance is due, or if aproduct or component has been recalled, or if a mechanical problem hasbeen found in a component such that all like components may need to bechecked.

In embodiments, medical RFID tags 2118 may facilitate managinginventories of medical supplies, medical kits, medical instruments, andthe like. A medical RFID tag 2118 may allow an inventory system to trackthe number of a particular item that is on hand, and may also allow thetracking of the usage pattern for the item. Raw usage data may then beassociated with other data pertaining to patterns of hospitaladmissions, diagnostic or therapeutic patterns, demographics, and thelike. In addition, usage of one item may be associated with usage ofother supplies, kits, instruments and the like. By accumulating andorganizing such information, a health care system may make predictionsabout the inventory that it needs to maintain. For example, bymonitoring the medical RFID tags 2118 associated with medical supplies,a health care system may determine that use of bandages, IV setups,suture materials and surgical instrument kits all rise and falltogether, correlated with the number of trauma patients seen in theemergency room. The emergency room may see an increase in traumapatients on weekend nights, on holidays, and in association with certainsporting and entertainment events. A health care facility may thenorganize its inventory to match its anticipated needs.

In embodiments, a medical RFID tag 2118 associated with medical suppliesmay permit a “smart shelf” functionality, permitting the use of suppliesto be monitored and optionally correlated with usage patterns, andfurther permitting efficient ordering and stocking of supplies in atimely manner to avoid overstocking and to avoid shortages. The medicalRFID tag 2118 may contain information about expiration dates associatedwith medical supplies so that supplies may be made available for usebefore the expiration date, and so that supplies whose expiration dateshave passed are readily identified for discard.

In embodiments, a medical RFID tag 2118 associated with may beassociated with kits containing individual pieces of equipment used formedical or surgical interventions. The medical RFID tag 2118 may permittracking of the components in kits (e.g., stents, catheters, implants,implantable devices and components thereof), as well as tracking of thekits themselves. The medical RFID tag 2118 may permit the location ofcomponents within kits, for emergency purposes, for maintenance or forrecalls.

In an embodiment, identifying information may be recorded on the medicalRFID tag 2118, to include for example the OEM information, repairenterprise information, component number, serial number, componentrevision level, or the like. This information may be applied as thecomponent is produced, revised, repaired, or the like to provide atraceable history of the manufacture of the component. The identifyinginformation may become the base information to allow the component to betracked though out the component's operational life cycle.

In an embodiment, the storing of information for the above capabilitiesmay be implemented using different memory configurations such as publicmemory, private memory, encrypted memory, read/write memory, writeonce/read many memory, read only memory, or the like. For example, themedical RFID tag 2118 may have information that should not be changedsuch as component number and serial number, therefore the some or all ofthe component's identifying information may be stored in write once/readmany memory. This would allow the OEM to write the component identifyinginformation but not allow anyone else to change this information. Inanother example, there may be enterprise only information that may bestored using encryption memory so only the enterprise may read theinformation. For example, a medical RFID tag 2118 worn or carried by apatient may contain medical record information that is encrypted to beread only by properly authorized health care personnel, so as to protectpatient privacy.

As previously described, a medical RFID tag 2118 providing the aboveinformation capabilities may include such features as RFID node chipredundancy, distributed memory, environmental capability, capability ofreading external sensor information, or the like. In an embodiment,these capabilities may be used individually or in combination. Themedical RFID tag 2118 may further have two or more RFID node chips thatprovide redundancy, increased memory, environmental resistance, andexternal sensor reading. In an embodiment, the RFID node chip redundancymay be provided by at least one RFID node chip redundant to at least oneother RFID node chip on the medical RFID tag 2118. The redundancy of theRFID node chips may allow the medical RFID tag 2118 to continue toprovide functionality even if one or more of the individual RFID notechip become damaged. For example, a medical RFID tag 2118 containingfour RFID node chips may continue to read and write information even ifone of the RFID node chips was to become damaged and stop functioning.In an embodiment, at least one of the remaining three RFID node chipsmay assume the function of the damaged RFID node chip so the medicalRFID tag 2118 may continue to store and transmit information.

In embodiments, a medical RFID tag 2118 may be implanted within apatient in association with an implantable medical device. Such animplantable medical RFID tag 2118 may be integrated with the medicaldevice in such a way as to be biocompatible. For example, the medicalRFID tag 2118 may be imbedded beneath the surface of the implantedmedical device, or it may be covered with a biocompatible material. Amedical RFID tag 2118 that is implanted may carry out the same functionsas a medical RFID tag 2118 that is associated with a medical device orcomponent thereof used externally. For example, the implanted medicalRFID tag 2118 may permit tracking of the device or a component thereof.As another example, the medical RFID tag 2118 may be associated withsensors that record parameters indicating the environmental orphysiological conditions to which the sensor is exposed. The medicalRFID tag 2118 may record the parameters to document device performance.The medical RFID tag 2118 may also transmit a signal in the event thatthe sensor indicates an environmental or physiological condition outsidean acceptable range. A sensor incorporated in a vascular graft, forexample, may identify a blood pressure outside the normal range. Anassociated medical RFID tag 2118 may then provide a signal to amonitoring system that indicates the abnormal parameter. A sensorincorporated in an implanted insulin pump, for example, may identify anabnormally high or low blood glucose level. An associated medical RFIDtag 2118 may then provide a signal to a monitoring system, oralternatively may signal the pump itself to alter its insulin dose. Asensor incorporated in a heart valve, for example, may monitor eachvalve cycle and transmit this information to the medical RFID tag 2118,which in turn may record the number of valve cycles, or record thestresses placed on valve components, or transmit signals correspondingto such information to monitoring systems. The exposure of the valve tostresses imposed by the cardiac cycle may then be monitored, andabnormal stresses or stress responses may be signaled.

If dimensionally adapted to the size and shape of a particular medicaldevice, the medical RFID tag 2118 may be attached thereto orincorporated therein. In other embodiments, the medical RFID tag 2118may be implanted at the same time as a medical device, to receivesignals from sensors or to carry information regarding the device itselfor its use. For example, a medical RFID tag 2118 may be implantedsubcutaneously at the same time that a heart valve, vascular graft,infusion pump, or the like, is implanted at the appropriate anatomiclocation. A medical RFID tag 2118 associated with an implanted medicaldevice may also be wearable or portable by the patient, e.g., as anelectronic medical identification card, band or medical alert bracelet.

A medical RFID tag 2118 associated with a medical device may receiveinformation from sensors may use a wireless interface or may behardwire-connected to the sensors, as the anatomic placement positionpermits. Additionally, the medical RFID tag 2118 may be able tocommunicate with more than one sensor using either a wired or wirelessconnection. In an embodiment, a medical RFID tag 2118 may network anumber of sensors together to collect and save the sensor information. Anetworking interface may be a separate device from the medical RFID tag2118, or may be part of the medical RFID tag 2118, or a combination ofseparate and integrated, or the like. Sensors may be associated with animplantable medical device, as described above. Sensors may also beassociated with a wide range of non-implantable medical devices andpieces of apparatus, as would be understood by those of skill in theart.

In embodiments, a medical RFID tag 2118 may be powered by ambientelectromagnetic waves, by a reader signal, by an electromagnet signaldevice, or the like. In an embodiment, the medical RFID tag 2118 mayread the associated sensors during power-up. For example, the medicalRFID tag 2118 may power up every time that a piece of equipment (e.g., aventilator or an anesthesia machine) is turned on. During the power-up,the medical RFID tag 2118 may read the data from the associated sensors.In another example, there may be a signal generator that powers up themedical RFID tag 2118 on a periodic basis to read the associated sensorsand record the readings. A signal generator may be associated with thepower supply for the device, for example, the battery pack for apacemaker or an implantable defibrillator. In an embodiment, a poweredsensor may be powered by an external source to provide a constant powersupply, so that the sensor may continuously measure and provide data tothe medical RFID tag 2118. A powered sensor may be powered by battery,by AC, by DC, by solar power, or the like. In an embodiment, a poweredsensor may be powered by the same supply that the medical RFID tag 2118uses. It may be understood by someone knowledgeable in the art thatdifferent types of sensors would be useful in different medicalcontexts, and that a variety of medical RFID tags 2118 may be employedin association with such sensors.

Referring to FIG. 28, a medical RFID tag 2118 may be used to facilitatepharmaceutical product tracking 2808 in ways similar to the medicalsupplies, devices and instruments tracking 2802 functionalitiesdescribed above. A container for a pharmaceutical product, for example,may bear a medical RFID tag 2118 with information about the drug, itslot number, its production history, and the like. In addition, acontainer for a pharmaceutical product may bear a medical RFID tag 2118with medical information associated with the product, for example itsdosage, its indications and contraindications, its interactions withother drugs, and the like. The medical RFID tag 2118 may permit trackingof the physical location of a pharmaceutical product within anenterprise or within a distribution network. Such tracking becomesuseful, for example, if a certain lot number of the product needs to berecalled.

Referring to FIG. 28, a medical RFID tag 2118 may be used to manage andstreamline pharmaceutical supply inventory and vending 2804 in wayssimilar to the medical supplies, devices, and instrument inventorymanagement described above. The medical RFID tag 2118 may allowmonitoring of available supplies of a pharmaceutical product. Suchmonitoring may be integrated with systems for ordering pharmaceuticalsupplies, so that appropriate amounts of the product will be on hand asneeded for patient care, without overstock or undersupply. As describedabove, an ordering system may be associated with a usage patternrecognition system, so that pharmaceutical products that tend to be usedtogether may be ordered in relation to each other. For example, if theusage of coumadin is noted to vary with the incidence of electiveorthopedic procedures in patients over forty-five, an ordering systemmay use the schedule for such procedures as a factor in orderingappropriate amounts of coumadin. Medical RFID tags 2118 forpharmaceutical products may comprise part of a “smart shelf” orderingprotocol, whereby inventory is tracked, use is monitored and predicted,and appropriate orders are placed.

In embodiments, a medical RFID tag 2118 associated with a pharmaceuticalproduct may interface with a medical RFID tag 2118 associated with anindividual patient. In embodiments, a patient-based medical RFID tag2118 may bear information about a patient's medical condition, maycontain data from the patient's medical record, and the like.Prescription data may be input into the patient-based medical RFID tag2118. As one example, a pharmaceutical product medical RFID tag 2118 maybe designed to query the patient-based RFID to ensure a match betweenthe product, for example, and the patient's prescription information. Asanother example, the pharmaceutical product medical RFID tag 2118 may bedesigned to query the patient-based medical RFID tag 2118 to ensure thatthe indications for the product correspond to the patient's diagnosedconditions. As another example, the pharmaceutical product medical RFIDtag 2118 may be designed to query the patient-based medical RFID tag2118 to ensure that the patient has no recorded allergies orcontraindications for the product.

In embodiments, the medical RFID tag 2118 for a pharmaceutical productmay durably bear information pertaining to the particular patient whowill be receiving it. A prescription for a patient, for example, may beconveyed to a pharmacy, and the medical RFID tag 2118 for the prescribedproduct may be updated by the pharmacist with information relating tothe prescription (e.g., dose, administration schedule, timing withrespect to meals, drug interactions, and the like). In embodiments, theinformation may be read by the patient or by the health care personnelwho are monitoring the patient's care. Information from the medical RFIDtag 2118 may be downloaded or transmitted, for example, to a handhelddevice, portable computer, desktop computer, computer network, or otherelectronic reader device, as would be understood by skilled artisans.

In embodiments, the prescription information from the patient-basedmedical RFID tag 2118 may interface with a medical RFID tag 2118 orother security system on the product's container to create a “smartpillbox,” wherein the container may be opened, for example, only atdesignated intervals or after the entry of an appropriate security code.Such arrangements may prevent use of the medication by unauthorizedusers, children, etc., or may be useful with patients who have troubleremembering a dosage schedule or recalling when they last took theirmedication.

As an alternative to correlating the product medical RFID tag 2118 witha patient-based medical RFID tag 2118, a health care workeradministering a medication may access the information on the productmedical RFID tag 2118 and correlate it with information from othersources, such as handheld devices, laptop computers, desktop computers,computer networks, hardcopy manuals or textbooks, or the like. Thehealth care worker may have to sign off after the administration of themedication by creating an electronic or hardcopy record, or by inputtingthe administration accountability information into the product medicalRFID tag 2118. In this way, the medical RFID tag 2118 may come tocontain information about its own utilization, permitting accountabilityrecording, accumulation of information for patient medical records andenterprise records, and the like.

In embodiments, a medical RFID tag 2118 for a product may acquire andretain information about the particular patient who has used theproduct, consistent with the requirements of medical privacy,confidentiality and informed consent, so that the product containerbearing the medical RFID tag 2118 may provide the pharmaceuticalmanufacturer with information about the clinical use of the product.This may facilitate acquiring data for clinical studies, such as thoserequired by the FDA. In embodiments, the medical RFID tag 2118 for aproduct may contain data indicating that the product had beenadministered to a particular patient. This information may betransmitted to other systems within a health care facility, interfacingfor example, with patient billing systems, utilization managementsystems, automated product ordering systems, or the like. Data carriedon a product's medical RFID tag 2118 may be encrypted or otherwiseprotected so that medical privacy and confidentiality is ensured.

In embodiments, an interlock system may prevent administration of apharmaceutical product to a patient where the product's and thepatient's RFIDs do not match. For example, such an interlock system mayprevent the administration of an overdose to a pediatric patient,prevent the administration of a drug to a patient known to be allergicto it, prevent the administration of a drug to a patient with knowncontraindications or drug interactions, and the like. In embodiments, aninterlock system may be imposed at any point in the supply chain for aproduct, with the product RFID having to match the code for a particularinstitution, patient care unit, or the like. In this way, inappropriatemedications would be detected upon delivery to a particular institution,patient care unit, or the like, minimizing the risk that inappropriatemedications would be provided to patients in such settings (e.g.,pediatric unit doses would not be accepted when erroneously delivered toa nursing home, or erectile dysfunction products would not be acceptedwhen erroneously delivered to a pediatric floor in a hospital). Aninterlock system may be absolute, or it may permit override by a medicalpractitioner. In the event of override, the interlock system may recordthe identity of the practitioner and the circumstances of the override.A system that requires a match between product and patient informationvia RFID interaction, and/or a system that provides an interlock in theevent of product/patient mismatch, may lead to fewer medication errorsand improved risk management.

By integrating pharmaceutical inventory systems and pharmaceuticaldelivery systems, a medical RFID tag 2118 associated with apharmaceutical product may permit the tracking of the product from itspoint of production or delivery throughout its product cycle, to itsultimate administration to the patient. The medical RFID tag 2118 mayrecord the individuals involved at the different stages of theadministration process, from the individual who receives the shipment inthe facility, to the individual in the pharmacy who receives the bulkshipment, to the pharmacist who distributes the product to the healthcare personnel, to the individual who administers the product to thepatient. A pharmaceutical tracking system 2808 may enhanceaccountability at every step throughout the distribution chain. Inembodiments, a pharmaceutical tracking system 2808 may assist insurveillance for the distribution of controlled substances, whichotherwise may be diverted from legitimate uses.

In another embodiment, the pharmaceutical product medical RFID tag 2118may contain information about that product which is accessible by amedical practitioner. A medical RFID tag 2118 on a pharmaceuticalproduct may act as a “virtual PDR” for the medical practitioner, withinformation about doses, indications and contraindications, druginteractions and the like. Such information may be downloadable by thepractitioner to a handheld device, a portable computer, a desktopcomputer, a computer network, and the like. The medical RFID tag 2118 ona pharmaceutical product may be updatable with new information as suchinformation becomes available. A pharmaceutical company may provideupdates of indications and the like, for example, as such data isaccumulated and is approved by the FDA. In this way, the pharmaceuticalproduct itself may bear the most up-to-date information about itself,its doses, indications and contraindications, drug interactions, and thelike.

A medical RFID tag 2118 for a pharmaceutical product may bedimensionally adapted for the particular product, its container or itspackaging, in such a way as to permit the medical RFID tag 2118 toachieve its goals. For example, a medical RFID tag 2118 may be attachedto a cap or a lid of a container in combination with an interlock orusage recording mechanism, the so-called “smart pillbox.” As anotherexample, a medical RFID tag 2118 may be associated with the membrane ofa product for intravenous injection, so that each withdrawal of theproduct through the membrane may be recorded on the medical RFID tag2118, or that each withdrawal of the product would require correlationwith a patient's RFID tag and/or accountability tracking. Inembodiments, the medical RFID tag 2118 may be associated with a sensorsystem. A sensor system may comprise one or a plurality of sensors thatrecord information such as twisting of a lid, change in pressure withina container, flow of fluid out of a container, administration of adiluting agent to the container, or the like.

With reference to FIG. 28, a medical RFID tag 2118 may be used forpatient tracking 2812. Patient tracking 2812 may involve physicaltracking within a health care facility. Patient tracking 2812 mayinvolve monitoring the progress of a patient throughout a protocol, sothat a health care worker may determine whether a patient has carriedout all the steps of a prescribed diagnostic or therapeutic sequence. Inembodiments, patient tracking 2812 via a medical RFID tag 2118 may beassociated with the creation of an electronic medical record, aspects ofwhich may be transported with the patient, for example as a hospitalbracelet, a medical ID card, a medical alert bracelet, a set of“dogtags,” or the like. Medical record information on the medical RFIDtag 2118 may then be accessed by health care providers or updated byhealth care providers, as appropriate.

In embodiments, a medical RFID tag 2118 may permit patient tracking 2812within a health care institution or health care system. Patient tracking2812 using a medical RFID tag 2118 may permit a nurse on a hospitalfloor, for example, to locate a particular patient who has gone off thefloor for tests, or a nurse in the operating room to keep track of atrauma patient who is en route from the emergency department. Themedical RFID tag 2118 may be associated with sensors within the hospitalfacility that act as “virtual checkpoints,” tracking the patient'sphysical location as the patient passes the particular sensor. Themedical RFID tag 2118 may also interface with check-in stations atdifferent parts of the hospital, so that the patient's medical RFID tag2118 records her arrival at the XRay department, physical therapy, theEKG lab, and the like. The “virtual checkpoint” or the check-in system,or the like, may permit patient tracking 2812 in association with apatient-based medical RFID tag 2118.

In embodiments, a medical RFID tag 2118 that permits patient tracking2112 as a patient “checks in” at particular units within a health caresystem may provide data that other information systems may use. Forexample, patient tracking 2112 using a medical RFID tag 2118 may allow apatient's presence at a particular unit to be recorded so that anattendance history may be recorded. This may allow the documentation ofpatient compliance with a treatment regimen, for example, physicaltherapy, diet counseling, Alcoholics Anonymous, or the like. Patienttracking 2112 as recorded on a medical RFID tag 2118 may be accessibleby a variety of patient care personnel, so inpatient and outpatienttests and treatments may be followed. A visiting nurse, for example, mayaccess the tracking information on the medical RFID tag 2118 todetermine that the patient has followed the recommended steps fordiabetes diagnosis, treatment and lifestyle counseling. As anotherexample, a visiting nurse may be able to determine that ananticoagulated patient has had prothrombin times measured on a regularschedule that are within the proper range. As yet another example, avisiting nurse may be able to determine that a patient has taken hermedications on an appropriate schedule, by interrogating thepatient-associated medical RFID tag 2118, by interrogating theproduct-based medical RFID tag 2118 in a patient's home (the “smartpillbox”), or the like.

In embodiments, patient tracking 2812 system may also permit a patient'sprogress to be followed through a complex sequence of diagnostic and/ortherapeutic steps. For example, a diagnostic protocol may require thattests be carried out in a certain sequence, and the patient may betracked from test to test to ensure that the sequence is followed in theproper order. As an example, a patient being evaluated for breastcancer, for example, may first need a mammogram, then an ultrasound,then a breast MRI, then a mammogram-guided biopsy. As that patientreceives each test, her medical RFID tag 2118 may be updated to recordthat the test was performed, so that she may proceed to the next step.In this way, a patient would not erroneously undergo testing out oforder. As another example, a patient tracking 2812 may ensure that apatient undergoing a procedure has accomplished all preliminarydiagnostic tests. In this example, a patient's medical RFID tag 2118 maybe updated as she has her pre-operative tests to indicate that they hadbeen performed, and this information would be read by operating roompersonnel before any surgery would be performed. A medical RFID tag 2118associated with a patient may serve a checklist function, so that thepatient cannot advance to a subsequent diagnosis or treatment step untilthe previous steps have been satisfactorily completed. Individualsperforming diagnostic or therapeutic steps or checking the results ofsuch steps may update the patient-associated medical RFID tag 2118 withtheir identifying data, so that accountability may be maintained foreach step.

In embodiments, a satisfactory completion of a diagnostic, therapeuticor pre-procedure sequence may be required before the patient undergoes aparticular intervention. The medical RFID tag 2118 may record thesatisfactory completion of each step, and may further be associated withan interlock system so that the patient may not undergo the interventionunless the sequence as recorded on the medical RFID tag 2118 issatisfactory. Entry into the operating room, for example, may involvethe communication of a patient's medical RFID tag 2118 with an interlockprogrammed in accordance with the preoperative requirements. In thisexample, a patient whose medical RFID tag 2118 indicates lack of testresults or unsatisfactory test results may be denied physical admissionto the operating room. Similarly, progress to the next stage in adiagnostic or therapeutic sequence may be protected by interlock, sothat the satisfactory completion of all preceding stages may be requiredbefore undergoing the next step in the sequence. A variety ofapplications combining a medical RFID tag 2118 with an interlock will beapparent to skilled artisans.

In embodiments, medical RFID tags 2118 used for patient tracking 2812may interface with other error-management systems to decrease theincidence of clinical errors. As an example, a medical RFID tag 2118 mayprevent “wrong side” surgery by containing independent information aboutwhich side of the patient needs the surgery, or by allowing a patient'sposition for surgery to be mapped to a protocol for operating on aparticular side. A patient undergoing a left lung resection, forexample, may require positioning on the operating table with his rightside down. A medical RFID tag 2118 containing information about theprocedure planned for this patient may communicate with a positionsensor affixed to the patient so that a right-side-down position for theleft thoracotomy is ensured; with the proper (right) side down, thewrong (right) lung cannot be removed. As another example, a medical RFIDtag 2118 containing information about an organ to be removed may need tobe “checked off” at several different stages of patient preparation inthe operating room (e.g., positioning, prepping, draping) so that allpersonnel are “reminded” on a number of occasions about which siderequires the operation. A reader for the medical RFID tag 2118 mayinclude display means that provide a visual or an audible signalregarding the side for surgery.

A medical RFID tag 2118 may be dimensionally adapted for placementwithin the body, so that a biocompatible RFID may be implanted duringinitial procedures to identify tissues or organs for subsequentexcision, radiation treatment, etc. A medical RFID tag 2118 may beplaced directly during an exploratory procedure or a resection toindicate where post-operative radiation should be directed. A medicalRFID tag 2118 may be placed endoscopically in an abnormal organ ortissue to indicate which organ or organ section may require furthertreatment (e.g., resection, radiation, intraarterial chemotherapy, andthe like), thereby enhancing error management. A medical RFID tag 2118may be placed at the time of a biopsy, for example if a frozen sectionis abnormal, to designate the location of the tumor for furthertreatment (e.g., so that the leg with the bone tumor is removed insteadof the other leg, or so that the correct region of the body isirradiated to treat a tumor). A medical RFID tag 2118 placed during afirst procedure may be used with an interlock system, alert system,display system, or the like, to ensure that a subsequent procedure isdirected to the proper organ or anatomic region.

With reference to FIG. 28, a medical RFID tag 2118 may be used tomonitor or control patient ingress and egress 2814 and/or ingress andegress of employees 2810 or other personnel. As described above, amedical RFID tag 2118 may allow the tracking 2812 of a patient'sphysical location. In other embodiments, the medical RFID tag 2118 maypermit the monitoring or control of a patient's entry into various areaswithin the health care facility. In other embodiments, the medical RFIDtag 2118 may be useful to monitor or control the ingress or egress ofemployees from the health care facility or certain areas thereof.

In embodiments, the medical RFID tag 2118 may record the physicallocation of a patient. A patient-associated medical RFID tag 2118 mayrecord a patient's passage into certain areas or the patient's passagepast certain checkpoints. Moreover, a medical RFID tag 2118 may controla patient's entry into or egress from certain areas. Patients, ingeneral, are restricted from certain areas within a health carefacility, such as pharmacies, storage areas, clinical areas that areinappropriate, and the like. A medical RFID tag 2118 associated with apatient may prevent access into a prohibited or restricted area, forexample by locking the entryway, or by interfacing with an alarm system.A medical RFID tag 2118 may also prevent a patient from leaving the wardin a similar manner, creating a “virtual locked ward.”

In embodiments, personnel within a health care facility may be trackedin ways similar to the patient tracking 2812 systems and methodsdescribed above. A medical RFID tag 2118 may be used to determine thephysical location of health care personnel within a facility, or may beused to follow the path of a particular health care individual. Thetracking of personnel may interface with other systems, permitting, forexample, system-wide information to be gathered about the whereabouts ofparticular categories of individuals. In the event of an emergency, forexample, it may be useful to know where within the facility theanesthesiologists and respiratory therapists are located. A medical RFIDtag 2118 worn by or carried by such individuals may permit theirlocations within the facility to be identified.

In embodiments, identifying the location of certain personnel within ahospital may be correlated with other features of communication or othersystems within a hospital. For example, a selective paging system maypage those individuals closest to a particular emergency situation, ormay page those individuals whose location indicates that they are mostlikely to be available. In this example, a medical RFID tag 2118 mayshow the location of the cardiologist nearest to a cardiac arrest; usingthat information, the selective paging system may send out an emergency(“STAT”) page for that specific cardiologist. Other examples may bereadily apparent to those of ordinary skill

A tracking system for personnel may be correlated with other features ofa health care information system, for example to assist with staffing orother personnel management issues. In this example, a medical RFID tag2118 worn by or carried by nursing personnel may allow each individualto “check in” at the beginning of a shift when he or she reaches theassigned duty station within a hospital or the like. The location ofeach individual may be mapped onto a personnel chart that shows whichduty stations are adequately staffed and which duty stations requireadditional staffing. Such information may, for example, allowredistribution of available personnel to meet staffing needs, or mayallow additional personnel (e.g., off-duty or temporary nurses) to becalled upon to meet the staffing needs. As another example, suchinformation may interface with systems to permit adjustment orredistribution of patient admissions, based on personnel numbers andlocations of short-staffed areas. For example, information regarding thenumbers of nursing staff in a surgical ICU may be collected by medicalRFID tags 2118 worn by or carried by nursing personnel and relayed to acontrol center; the control center may respond to a shortage of nursesin the surgical ICU by recruiting nurses from other hospital areas(medical ICU, recovery room, and the like), by restricting newadmissions from other hospital floors, by redistributing patients toother ICUs, by closing the emergency room to new patients, or the like.Other examples may be readily apparent to those of ordinary skill

In embodiments, a medical RFID tag 2118 may track employeeingress/egress 2810, and/or be used as an adjunct to other securitysystems. A medical RFID tag 2118 may allow personnel to check into orout of the facility, so that there is a record of who is on-site. Suchinformation may be integrated with other systems in the facility, e.g.,communications systems. In such an example, a physician checking into ahospital facility may have a data set about the status of hisin-hospital patients downloaded into a handheld device or portablecomputer after his medical RFID tag 2118 is recognized upon check-in bythe hospital information system.

In other embodiments, a medical RFID tag 2118 may be used by an employeeto gain access to certain areas within the health care facility. Accessregulated by a medical RFID tag 2118 may be organized according to theindividual person's identity, the job description, the time of day, orthe like. As an example, a pharmacy supervisor may carry or wear amedical RFID tag 2118 providing her access to all areas of the pharmacy,including receiving areas, formulation areas, storage areas and thelike. The medical RFID tag 2118 worn or carried by a physical therapist,by contrast, may provide him access to none of these areas. Ananesthesia technician may carry or wear a medical RFID tag 2118 grantingaccess only to operating room pharmacy areas, and only during herworking hours. The anesthesia technician attempting to use the medicalRFID tag 2118 to gain access to an operating room pharmacy area duringnon-working hours may be denied access; moreover, a record of the accessattempt and/or an alarm may be generated. As another example, aspecifically encoded medical RFID tag 2118 may be necessary foraccessing patient medical records, so that only individuals involved incaring for a particular patient may have access to that patient'smedical records.

In other embodiments, a medical RFID tag 2118 may be employed to grantor restrict access for other individuals who are not employed by thehealth care facility. A vendor, for example, may be provided with amedical RFID tag 2118 that allows him access to an area of the hospitalfor a specified period of time. In this example, an individual like amedical devices sales representative may use his medical RFID tag 2118to gain access to the operating suite where he is to demonstrate the useof a particular product. However, the medical RFID tag 2118 issued tothis individual may not grant him access to any other area, and may betime-limited, so that his failure to leave the premises and check out bya certain time may, for example, send an alarm to hospital securitypersonnel. As another example, a visitor to a hospital may be issued amedical RFID tag 2118 that allows him or her to enter a specified areaof the hospital where he or she will be visiting a patient. The medicalRFID tag 2118 may be time-limited, so that the visitor's failure toleave the premises and check out by a certain time may, for example,send an alarm to hospital security personnel. Prior to obtaining amedical RFID tag 2118, the visitor may have to check in with security.Certain individuals (visitors whom the patient does not wish to see,abusive spouses, etc.) may, for example, be placed on a no-visit listand may be denied a medical RFID tag 2118 granting hospital access.Alternatively, a prospective visitor's name may need to be registered ona visitor list before a medical RFID tag 2118 granting hospital accessis issued. Other examples may be readily apparent to those of ordinaryskill

In embodiments, a plurality of RFID tags 102 may be programmed such thatthey operably act as a composite multi-tag 2902, that is, multiple RFIDtags 102 may be configured in the system to present such that they aretreated as if they were configured as one device. In embodiments, theplurality of RFID tags 102 may be realized as a composite multi-tag 2902at the physical tag 102 to reader 140 interface level, or at a higherlevel of abstraction in the system, such as in the reader 140, thecomputer/server 202, the application servers 148, in markets 150, or thelike. For example, and as illustrated in FIG. 29, the compositemulti-tag 2902 may be realized at the tag 102 to reader 140 interface byconfiguring the EPC numbers of the plurality of RFID tags 102A-C so thatone RFID tag 102A is identified as the primary, and the remaining of theplurality of RFID tags 102B-C, are identified as secondary. The primaryRFID tag 102A may thereafter act as the primary communications pointbetween the composite multi-tag 2902 and the reader 140, the primaryRFID tag 102A may provide a group interface to the reader 140, theprimary RFID tag 102A may provide a central memory collection point forthe plurality of RFID tags 102A-C, the primary RFID tag 102A may providea central functional coordination point for the plurality of RFID tags102A-C, and the like. In embodiments, the secondary RFID tags 102B-C,may be communicated through the primary RFID tag 102A, directly with thereader 140, through an RF coupling between RFID tags 102, through aphysical connection between RFID tags 102, and the like. In addition,the primary RFID tag 102A may be chosen to be physically capable oflonger range communications than the secondary RFID tags 102B-C, and theplurality of RFID tags 102A-C may have different physical memoryallocations. In embodiments, due to the connectivity between theplurality of RFID tags 102A-C, secondary RFID tags 102B-C may not needto be configured with an antenna 108.

In embodiments, when memory 3004 is spread across the plurality of RFIDtags 102A-C, the system may need to maintain certain associations. Forinstance, if there is a risk of multiple such RFID tag 102A-Ccombinations presenting at a reader 140 simultaneously, it may benecessary to maintain a reference or other means of determining whichRFID tags 102 are part of which combination. In addition, in order todetermine the logical ordering of memory 3004, individual tags 102within the combination may need to be uniquely identifiable, such thatthe memory 3004 they contain may be properly mapped. One such means ofmaintaining grouping and ordering may be to assign one RFID tag 102A asthe primary tag 102A, and supplemental tags 102B-C being assigned assecondary tags 102B-C. In embodiments, all to the RFID tags 102A-C maybe linked via data in their EPC banks. In embodiments, any functionalityspread across multiple devices, including sensor inputs, alertingmechanisms, and the like, may also be abstracted to present as if theywere implemented as one device.

Continuing in reference to FIG. 29, an example is presented to show howprogramming of the RFID tags 102A-C may identify the set of RFID tags102A-C as a composite multi-tag 2902. This example is meant to beillustrative, and not limiting in any way. One skilled in the art willrecognize alternate configurations for establishing the plurality ofRFID tags 102A-C such that they act as a composite multi-tag 2902. Inthis example, one of the RFID tags 102A is chosen as the primary, wherethe serial number of the primary, in this case ‘AAA’, may then be usedas the start of the EPC number for all the secondary RFID tag 102B-Cmembers of the composite multi-tag 2902. In addition, each of the RFIDtag 102A-C members may be assigned a member number, where for instancethe primary RFID tag 102A is numbered ‘1’, the next RFID tag 102B isnumbered ‘2’, the next RFID tag 102C is numbered ‘3’, and so on for therest of the plurality of RFID tags 102A-C that make up the compositemulti-tag 2902. In embodiments, the primary RFID tag 102A may also havean indication of the number of RFID tags 102A-C that make up thecomposite multi-tag 2902, such as by an identifier provided after theprimary RFID tag's 102A EPC number, in this case the number ‘3’ toindicate that there are three RFID tag 102A-C members making up thecomposite multi-tag 2902. With this programmed configuration, the reader140 may determine the configuration and EPC numbers of all RFID tag102A-C members by reading only the primary RFID tag 102A information.For instance, when the reader 140 extracts the EPC and supplementalnumber XXXX-3, and the primary RFID tag's 102A serial number AAA, thereader may then be able to derive the EPC numbers for the rest of theRFID tags 102B-C making up the composite multi-tag 2902. That is, fromthe primary RFID tag's 102A serial number of ‘AAA’, and the EPCsupplemental number of ‘3’, the reader now knows there are a total ofthree RFID tag 102A-C members, including the primary RFID tag 102A,where the secondary RFID tag 102B-C EPC numbers are ‘AAA2’ and ‘AAA3’.In embodiments, all of the RFID tag 102A-C members may also be provideda group number to identify all the member RFID tags 102A-C within acomposite multi-tag 2902, such as a group number of ‘1’ in this example.

In embodiments, the plurality of RFID tags 102 may be realized as acomposite multi-tag 2902 at a higher level of abstraction in the system.For example, and referring to FIG. 30, each of the plurality of RFIDtags 102A-C may be individually read by the reader 140, where the reader140 may not be required to immediately recognize that the plurality ofRFID tags 102A-C are associated with one another, and where the reader140 may collect information from the plurality of RFID tags 102 andeither processes the collected information to associate the plurality ofRFID tags 102 as a composite multi-tag 2902, or send the information onto other components in the system for like processing, such as to thecomputer/server 202, the data storage 144, the application servers 148,the markets 150, and the like. In embodiments, the processing may beperformed through software that associates the plurality of RFID tags102 to a composite multi-tag 2902. Further, the information collectedfrom the plurality of RFID tags 102 may be associated together as a partof the single composite multi-tag 2902 entity. For instance, the memorycollected from the plurality of RFID tags 102A-C may be assembled into acontiguous memory, where thereafter the contiguous memory is associatedwith the composite multi-tag 2902 rather than the individual RFID tags102A-C. In embodiments, other RFID tag 102 functions may also beassociated with the composite multi-tag 2902, such as processorfunctions, sensor functions, and the like. In embodiments, associationsbetween RFID tags 102 may be retained off the tag 102, such as in thedata storage 144, in a database, by algorithmic processing of data suchas with unique Ids encoded with the RFID tags 102, and the like.

Referring to FIG. 30, in embodiments the plurality of RFID tags 102A-Ccomprising the composite multi-tag 2902 may be mounted on a placementfacility 3002, where the placement facility 3002 may be a substrate, asilicon wafer, a ceramic platform, a metal surface, a box, a container,a shipping container, and the like, where the plurality of RFID tags102A-C may be spread out while maintaining their collective identity asa composite multi-tag 2902. In embodiments, the primary RFID tag 102Amay be capable of longer range communications 3008A than the secondaryRFID tags 102B-C, such as being physically equipped with a largerantenna 108A. As a result, the primary RFID tag 102A may be detected3008A by the reader 140 at greater distances than the secondary RFIDtags 102B-C, which may be equipped with smaller antennas 108B-C. In thisway, the primary RFID tag 102A may act as a beacon 3008A to the reader140 for location of the composite multi-tag 2902 at greater distancesthan the reader 140 can detect the secondary RFID tags 102B-C. Inembodiments, as the reader 140 is brought closer to the compositemulti-tag 2902, the reader 140 may be able to directly communicate3008B-C with the secondary RFID tags 102B-C. In embodiments, a systemwhere the composite multi-tag 2902 is influenced by coupling effectswith the tagged item may achieve a performance boost beyond theperformance that would be expected in free space.

In embodiments, the RFID tags 102A-C comprising the composite multi-tag2902 may be able to communicate between themselves 3008D-F, such asthrough the larger antenna 108A being electrically coupled by closeproximity to the smaller antennas 108B-C which may give them the benefitof a larger antenna 108A. This may enable the shorter range tags 102B-Cto be read at a greater distance. In embodiments, electrical couplingmay use capacitive coupling, inductive coupling, coupling through thetagged product, and the like. In addition, communication between thesecondary RFID tags 102B-C and the primary RFID tag 102A may beimplemented by direct connection, such as by soldering, adhering,crimping, and the like. In embodiments, there may be more than one longrange RFID tag 102A provided on the composite multi-tag 2902 in order toimprove the communication between the reader and the composite multi-tag2902. In embodiments, a system where the composite multi-tag 2902 maycombine with a tagged item using capacitive, inductive, directconnection, or other coupling means, may use the tagged item as aprimary antenna component for the purposes of communication.

In embodiments, RFID tags 102 may be applied to a spatially diverseobject, where the RFID tags 102 may be associated with a substantiallyidentical name plate function, and thus may be used to maximize theprobability of detection (e.g. allowable read angles). In this instance,user memory may be distributed across the individual RFID tags 102 bymeans similar to those described herein.

In embodiments, the RFID tags 102A-C comprising the composite multi-tag2902 may be able to share RFID tag memory 3004A-C contents as a resultof communications 3008D-F between the plurality of RFID tags,communications 3008A-C between the RFID tags 102A-C and the reader 140,and the like. In embodiments, the RFID tags 102A-C may contain differentamounts of physical memory 3004A-C. For instance, the secondary RFIDtags 102B-C may have a larger allotted physical memory 3004B-C than theprimary RFID tag 102A because the secondary RFID tags 102B-C havesmaller antennas 108B-C, and so have a larger space available forphysical memory 108B-C. In embodiments, the physical memory 3004A-C ofthe composite multi-tag 2902 may be identified as a continuous virtualmemory space to the reader 140, such that the reader 140 does not haveto be aware that the composite multi-tag 2902 is made up of separatephysical memories 3004A-C, separate physical RFID tags 102A-C, and thelike. In embodiments, the distributed larger effective memory may allowfor user memory space, provide prototyping larger memories before theyare available and allowing the swapping of RFID tags 102A-C when theybecome available, allowing for error correction in the event of afailure of an RFID tag 102A-C, and the like. In embodiments, the usermemory from the plurality of RFID tags 102 may be mapped into a logicaladdressing space to appear as a single RFID tag 102, such as thecomposite multi-tag 2902. This mapping may be implemented by software inthe reader 140, in the computer/server 202, in the application servers148, in the markets 150, and the like, or implemented in at least one ofthe RFID tags 102A-C.

In embodiments, memory configurations may utilize encoding within theRFID tags 102, such as in data written into an EPC bank, into usermemory, into configuration memory, into program memory, and the like. Inembodiments, a system where additional memory resources, including forexample, EPC memory banks (including unused memory beyond an EPC code),password memory, other available memory, and the like, may also bemapped into the logical memory space to appear as user memory. Inembodiments, a system where the memory from multiple tags may be mappedinto memory arrangements other that one contiguous user bank, such asfor example into an extended EPC bank, multiple user banks, and thelike.

In embodiments, the composite multi-tag 2902 may include any combinationof RFID tag 102 capabilities, such as memory, processing, sensorinterfaces, antennas, and the like. In embodiments, the informationassociated with a composite multi-tag 2902 may be associated withprocessing, such as with compression algorithms, encryption algorithms,authentication algorithms, encoding algorithms, and the like. Thecomposite multi-tag 2902 may utilize these RFID tag 102 capabilities inserial, parallel, and the like, such as processing on one RFID tag 102Band storing information on a second RFID tag 102C, storing the sameinformation on multiple RFID tags 102, simultaneously using multiplelong range RFID tags on the composite multi-tag 2902 to enhancecommunication characteristics with the reader, and the like. Inaddition, the composite multi-tag 2902 may contain a mixture ofdifferent types of RFID tags 102, such as a combination of custom RFIDtags 102 and off-the-shelf RFID tags 102, all custom RFID tags 102, alloff-the-shelf RFID tags 102, passive RFID tags 102 and active RFID tags102, and the like, where custom RFID tags 102 may contain anyconfiguration of nodes, chips, antennas, sensors, processing, memory,and the like, as described herein. In embodiments, a system where memorymay be mapped using the techniques across multiple devices incombination with redundant encoding techniques, such that the compositemulti-tag 2902 may achieve a level of fault tolerance when one or moredevices within it fails or degrades.

In embodiments, a user may be enabled to exchange data with an RFID tagthrough an RFID drive management facility as a seamless extension of afiling system within a computing device such that the RFID tag andassociated RFID tag data may be managed in a manner that is logicallyconsistent with other items within the file system, where the computingdevice may be a server, desktop computer, laptop computer, smart phone,and the like. The RFID drive management facility may provide formanagement of the RFID tag, managing the identity of an RFID tag,recognizing the presence of an RFID tag, and the like. For instance, theRFID tag may appear to a computer in a similar way as a file folder orflash drive would appear, where the user is able see that the RFID tagis present, to move data to and from the RFID file system elementthrough drop-and-drag actions, change the identity of the RFID tag, andthe like, where the presence of the RFID drive management facility maybe transparent to the user. In embodiments, the computing device mayhave software components to convert data structures between the formatof an RFID tag memory and that of a computer file system, such as forthe Windows operating system, the Apple operating system, Androidoperating system, iOS, Windows CE/Mobile, and the like. Although thisdisclosure refers to RFID tags, one skilled in the art will appreciatethat the methods and systems of the present invention may be applied toany short range RF identification system, such as for near fieldcommunications (NFC) enabled devices.

Referring to FIG. 31, an RFID tag 3102 may be accessed via an RFID drivemanagement facility 3104 resident on a computing device 3108 through anRFID interrogator 3110 (e.g. an RFID reader) connected to, or integratedwith the computing device 3108. The RFID drive management system 3104may provide a means for user and system interaction with an RFID tag3102, where RFID tag data 3114 stored on the RFID tag's memory 3112 istransferred between the RFID tag memory 3112 and the computing devicefile system 3118 as data 3120 formatted for display and edit through thecomputer device's computer interface 3122. The RFID drive managementfacility may make it much easier to use RFID tags, which may not requirespecial software, consider or implement programming solutions, tagmemory layouts, and the like. When the RFID drive management facility isdeployed on a computing device with an attached or embedded RFID reader,an RFID tag appearing within range may be mounted within the file systemof the computing device. For instance, the RFID tag may be mounted as adedicated drive (e.g. ‘T:\’), as a folder (e.g. ‘Computer>Tags>Tag Name’on a conventional Windows based PC), as a directory on a Unix, Linux orAndroid based system (e.g. ‘\mnt\tags\tagname’), and the like.

In embodiments, the RFID drive management facility may provide RFID tagsand associated RFID data across a networked system, where theprocessing, RFID readers, and the like, may not be locally resident withthe computing device, such as where the file system is perceived by thelocal user separate from the locally resident capabilities or physicalarchitecture associated with the RFID interrogator and the location ofthe RFID tag. For instance, and referring to FIG. 32, an RFIDinterrogator 3110 may interface with a computing device 3202, where theRFID drive management facility 3104 may manage the interface andexchange of data with the RFID tag 3102. The computing device 3202 mayinterface with at least one of a plurality of computer devices 3208across a network 3204. In this wider network context, the RFID tags mayhave uniform resource locations, such as if they were network or webpages/servers in their own right. In such a case, a user might interactwith a remote tag via a web browser with RFID drive management facilityproviding a similar conversion between tag data format and html format.

The RFID drive management facility may enable changing the identity ofan RFID tag. For example, changing the EPC on EPCglobal compatible tagmay require the user to only have to rename the associated drive or afolder such as through using Windows Explorer, the desktop environmentor other conventional tools provided as part of the computer deviceoperating system, with no need for a special application.

The RFID drive management facility may allow records to be stored andrecovered from the RFID tag by treating them as conventional files, e.g.they may be dragged and dropped into the RFID tag by dragging anddropping them into the drive or folder representing the RFID tag, andedited in situ by for example double clicking them. The RFID drivemanagement facility may deploy advanced serialization andde-serialization algorithms to convert the files to and from the RFIDtag memory format, and a conceptual RFID tag file system, which mayallow these files to be held in a manner that maps onto a hierarchicaltree paradigm used by modern computer systems. In embodiments, this maybe transparent to the user, where all the user may know is that they cansee and interact with the RFID tag just like they can a computer device,such as a PC, a portable flash drive, and the like, as described herein.

The RFID drive management facility may transform the user experiencewhen interacting with RFID tags, and greatly simplify system deployment.For example, consider the case where an RFID tagged asset travelsthrough multiple locations adding information to the RFID tag at eachstage, such as a document requiring multiple levels of approval. Anormal deployment scenario would likely involve writing a specialpurpose application for this function. By running the RFID drivemanagement facility on each computing device, conventional applicationssuch as Microsoft Excel may be used for this function, changing the filedirectory to that of the RFID tag.

In embodiments, the RFID drive management facility may map RFID tagsonto file system elements, such as disclosed herein. Records on an RFIDtag may map onto files with a tag. Using a native file ‘rename’ commandwithin the operating system may change tag identity and record names. Afile name representing the tag may be a hexadecimal conversion of thetag identity, a general purpose string, a human readable form of thedata used to encode the tag identity, and the like. For example, a filename may be encoded in a manner similar to the EPC URI defined in theGS1/EPCglobal Tag Data Standard 1.6. Records may be added to the RFIDtag by saving, by drag-and-drop, and the like, and edited by techniquessuch as edit, double click, and the like. Data held on the tag may notbe an exact binary match of the mapped file contents, but optimized viatechniques such as indexing and compression for efficiency. Techniquesused to store data on the tag may comply with a defined tag data format,for example ATA Spec 2000. The RFID drive management facility mayinterrogate an RFID tag and assign a converter that maps between tagdata format and computer file format based on the format of the tagdata. Edits to records may be held as changes (e.g. by diff encoding)rather than by overwriting the existing record, such that a full audittrail of changes may be recovered. RFID tag identity, and/or one or morefolders or records, may be secured via cryptographic means such as butnot limited to encryption, hashing and digital signatures. Cryptographicalgorithms used to secure data may operate on and include the uniquemanufacturing identity of the RFID tag (e.g., as its chip serial number)to prevent genuine data being considered authentic when copied toanother (counterfeit) tag. A control menu for the RFID drive managementfacility may be accessed by clicking or right clicking a status icon(e.g., such as a user would access printer spooling controls). Anengineering user interface may show tag memory contents (such asoptionally decoded). A secondary application programmer interface mayallow RFID tags to interact with special purpose programs whileretaining interoperability with the RFID drive management facility. RFIDtags may be used without a dedicated tag file system and presented tothe user as a raw memory dump, which may be edited (and hence change thetag memory) using conventional tools such as spreadsheets, wordprocessors, text editors, and the like. Free space may be shown as anotional free space file having size equivalent to or representing thefree memory on the RFID tag when the tag is mounted as a folder ratherthan a drive. For example, it may make sense to map RFID tags to foldersif more than one tag is present, but folders may inherit free space fromthe drive rather than having their own free space. With a drive mapping,the drive may show the true free space. Conventionally defined memorylayouts may be mapped onto computer application files. For example, amaintenance record in Spec 2000 could be edited within Microsoft Excelwith the mapping converting between the Excel binary format and theASCII name-value pairs format of Spec 2000 in a manner that istransparent to users (i.e. this technique may work with any definedmemory format given the right mappings). Multiple layouts may coexistwithin the same RFID tag and be accessed by the RFID drive managementfacility (e.g., a public region in ATA Spec 2000 format, and one or moreoptionally private regions in a different format, such as the ‘diffing’file system described herein).

In embodiments, the RFID drive management facility may provide forinterfaces within a web-based Internet cloud environment. For instance,interfacing with a cloud environment may addresses needs associated withthe fact RFID tags often pass through many locations/organizationscollecting data (e.g. maintained aviation parts, where once the RFIDtagged part is in the field it is traditionally difficult to get addedinformation back to the organizations needing it until the part returnsto their possession). The cloud configuration may be implemented as atrusted third party service (e.g. with an enabling application) whereRFID tag information may be automatically synchronized with the back-endsystems of organizations having interest in the RFID tag informationwhenever the tag is read. The system may allow users to specify the datathey desire and the data they allow others to have, and may providemeans of cryptographically ensuring privacy (e.g. via encryption), andauthenticity (e.g. via digital signatures) such that information issecurely disseminated. A cloud-based server may be capable ofcommunicating with client software to provide cryptographic credentialssuch as public/private keys that can be used by the RFID drivemanagement facility. The authentication process may optionally includethe RFID tag identity as described herein to prevent counterfeit tags tobe created by copying data. In embodiments, the cloud implementation maybe considered a ‘switchboard’ that connects organizations with the dataon their RFID tags whenever a tag appears at a read point (i.e. a devicerunning the RFID cloud implementation that has a network connection), asa value added network (VAN) for EDI, and the like.

In embodiments, methods and systems may be provided for managing RFIDtags, where an RFID tag and associated RFID tag data are presented to acomputing device through an RFID drive management facility as a seamlessextension of a logical file system within the computing device such thatthe RFID tag and associated RFID tag data can be managed in a mannerthat is consistent with other items within the file system. Thecomputing device, or computer system, may communicate with the RFID tag,such as through a connection to an interrogator, through a networkconnection, and the like. In embodiments, the system may be implementedas a computer implemented system of managing RFID tags, such ascomprising an RFID tag, a memory comprising instructions, a processorreceiving data from the RFID tag, and performing the steps of providinga RFID drive management facility on the computer system, the computersystem having a logical file system, presenting an RFID tag as anextension of the logical file system, providing the ability to managedata on the RFID tag in the logical file system, and the like.

In embodiments, methods and systems may provide for computerfunctionality, where the RFID tag may be mounted as a file systemelement accessible within the local and network file system available tothe computing device. The file system element may be a drive, folder,network share, uniform resource location, and the like. The identity ofthe RFID tag may be changed by changing the name of the drive, folder,network share, uniform resource location (e.g. including both local areaand wide area/internet locations), and the like. The name may be in oneof a plurality of representations, such as hexadecimal, human readablefields constituting the identity separated by delimiters, generalpurpose naming string, and the like. The RFID drive management facilitymay operate autonomously and transparently to the user with minimalinteraction, such that the ordinary user interface for reading andwriting data is the same as the file system. The RFID drive managementfacility may be implemented as a process, daemon or other capabilitywithin the run-time or operating system; a device driver either in therun-time kernel or application space, an application; a service; aremote procedure call (or equivalent capability), and the like. Thecomputer device may be a server, a desktop computer, a laptop computer,a tablet computing device, a smart phone, and the like.

In embodiments, methods and systems may provide for editing and writingback to the tag where the RFID tag data is edited on the computingdevice and transferred to the RFID tag. The editing may be providedwithin an operating system, a user interface environment, and the like.The editing may include copy-and-paste and drag-and-drop techniques. Theediting may provide changes to file system elements by an application,run time system, and the like, within the computing device. The editingmay comprise copying, renaming, deleting, and the like. The editing maybe provided by at least one of a spreadsheet application, databaseapplication, word processing application, text editor application, andthe like on the computing device. The editing may allow an existingapplication to read and write data to and from tags through itsconventional file handling interface (versus requiring RFID specificfunctionality). The editing may be provided by a web browser, and theRFID tag presented as if it were a web page or other named resourcelocation.

In embodiments, methods and systems may provide for cloud or local areastorage, transferring the RFID tag data from the computer device to aserver-based cloud or local area network storage facility, such as wherethe RFID tag data may be made available to a second computer device. TheRFID tag data may be mounted at a uniform resource location, as anetwork file share, and the like.

In embodiments, methods and systems may provide for RFID tag structuresand configurations described herein, including multi-node RFIDconfigurations, single-node RFID configurations, composite RFID tagconfigurations, usage of one-time programmable (OTP) memory structureson the RFID tag, and the like. For instance, the RFID tag interfacingwith the RFID drive management facility may utilize OTP memoryconfigured as emulated multiple-time programmable (eMTP) memory. TheRFID drive management facility may then manage reads and/or writes withthe RFID tag as if accessing true multiple-time programmable memory,such as available in RAM, flash memory, a hard drive, and the like. Inthis way, the RFID tag, who's access is managed through the RFID drivemanagement facility, may appear to the user of the computing device assimilar to other file system elements on the computing device. Forexample, the user may access the RFID tag as a storage drive icon on thedesktop of the computer device as if the RFID tag was a portable flashmemory drive plugged into the computing device, where in reality thememory being accessed is OTP memory on the RFID tag configured as eMTPmemory, as described herein. In another example, the RFID tag may be amulti-node RFID tag as described herein, where each RF node for instanceis shown as a separate memory storage icon on the desktop of thecomputing device. Although only a few examples have been provided forhow the RFID drive management facility may be utilized in combinationwith the RFID structures and configurations as described herein, oneskilled in the art will recognize the ability of the RFID drivemanagement facility to interface a computing device to other structuresand configurations described herein.

In embodiments, methods and systems may provide for file formatting,where the RFID drive management facility provides a mapping of an RFIDdata format to a computer file format. The RFID drive managementfacility may simultaneously provide mapping to a plurality of computerfile formats, where one of the plurality of computer formats may be araw file format showing sequential data memory content as the data isstored on the RFID tag. The RFID drive management facility maysimultaneously provide mapping to a plurality of tag data formats. TheRFID drive management facility may identify an RFID tag data format andassign a converter to translate and convert between the file formatwithin the computer system and the data format within the tag. The RFIDdrive management facility may provide a mapping of a computer fileformat to an RFID data format. The data format within the RFID tag maybe an exact representation of the file format within the computingsystem. The RFID drive management facility may provide a data formatwithin the RFID tag with additional processing to convert between theRFID tag data format and the computing system format, where theadditional processing may include data compression, delta coding (suchthat changes to data are stored and resaved unchanged data is notstored), and the like. Changes may be time-stamped so that the exact tagstate at a particular date and time may subsequently be recovered.Digital signature information may be added to validate data or tagintegrity.

In embodiments, methods and systems may provide for managementcapabilities, such as where control functionality for the RFID drivemanagement facility may be accessed from a control icon, a status icon,and the like within a user desktop. The status icon of the managementcapability may be changed to indicate the state of the reader. Forinstance, animated green arcs within an icon may show that the RFIDinterrogator is reading, and animated red arcs may show that the RFIDinterrogator is writing. The RFID drive management facility may beintegrated with and managed by network management software orcapabilities used to manage network and computing infrastructure.

In embodiments, methods and systems may provide for an RFID interrogator(e.g. an RFID reader, a NFC reader). The RFID interrogator may beinterfaced to the RFID drive management facility via a dedicatedconnection, such as an RS232 connection, a USB connection, and the like.The RFID interrogator may be interfaced via a network. The RFIDinterrogator may be incorporated within the computing device. Forinstance, the RFID interrogator may be integrated into a rugged RFIDhand-held, an NFC enabled tablet or cell phone, and the like.

While only a few embodiments of the present invention have been shownand described, it will be obvious to those skilled in the art that manychanges and modifications may be made thereunto without departing fromthe spirit and scope of the present invention as described in thefollowing claims. All patent applications and patents, both foreign anddomestic, and all other publications referenced herein are incorporatedherein in their entireties to the full extent permitted by law.

The methods and systems described herein may be deployed in part or inwhole through a machine that executes computer software, program codes,and/or instructions on a processor. The present invention may beimplemented as a method on the machine, as a system or apparatus as partof or in relation to the machine, or as a computer program productembodied in a computer readable medium executing on one or more of themachines. The processor may be part of a server, client, networkinfrastructure, mobile computing platform, stationary computingplatform, or other computing platform. A processor may be any kind ofcomputational or processing device capable of executing programinstructions, codes, binary instructions and the like. The processor maybe or include a signal processor, digital processor, embedded processor,microprocessor or any variant such as a co-processor (math co-processor,graphic co-processor, communication co-processor and the like) and thelike that may directly or indirectly facilitate execution of programcode or program instructions stored thereon. In addition, the processormay enable execution of multiple programs, threads, and codes. Thethreads may be executed simultaneously to enhance the performance of theprocessor and to facilitate simultaneous operations of the application.By way of implementation, methods, program codes, program instructionsand the like described herein may be implemented in one or more thread.The thread may spawn other threads that may have assigned prioritiesassociated with them; the processor may execute these threads based onpriority or any other order based on instructions provided in theprogram code. The processor may include memory that stores methods,codes, instructions and programs as described herein and elsewhere. Theprocessor may access a storage medium through an interface that maystore methods, codes, and instructions as described herein andelsewhere. The storage medium associated with the processor for storingmethods, programs, codes, program instructions or other type ofinstructions capable of being executed by the computing or processingdevice may include but may not be limited to one or more of a CD-ROM,DVD, memory, hard disk, flash drive, RAM, ROM, cache and the like.

A processor may include one or more cores that may enhance speed andperformance of a multiprocessor. In embodiments, the process may be adual core processor, quad core processors, other chip-levelmultiprocessor and the like that combine two or more independent cores(called a die).

The methods and systems described herein may be deployed in part or inwhole through a machine that executes computer software on a server,client, firewall, gateway, hub, router, or other such computer and/ornetworking hardware. The software program may be associated with aserver that may include a file server, print server, domain server,internet server, intranet server and other variants such as secondaryserver, host server, distributed server and the like. The server mayinclude one or more of memories, processors, computer readable media,storage media, ports (physical and virtual), communication devices, andinterfaces capable of accessing other servers, clients, machines, anddevices through a wired or a wireless medium, and the like. The methods,programs, or codes as described herein and elsewhere may be executed bythe server. In addition, other devices required for execution of methodsas described in this application may be considered as a part of theinfrastructure associated with the server.

The server may provide an interface to other devices including, withoutlimitation, clients, other servers, printers, database servers, printservers, file servers, communication servers, distributed servers andthe like. Additionally, this coupling and/or connection may facilitateremote execution of program across the network. The networking of someor all of these devices may facilitate parallel processing of a programor method at one or more location without deviating from the scope ofthe invention. In addition, any of the devices attached to the serverthrough an interface may include at least one storage medium capable ofstoring methods, programs, code and/or instructions. A centralrepository may provide program instructions to be executed on differentdevices. In this implementation, the remote repository may act as astorage medium for program code, instructions, and programs.

The software program may be associated with a client that may include afile client, print client, domain client, internet client, intranetclient and other variants such as secondary client, host client,distributed client and the like. The client may include one or more ofmemories, processors, computer readable media, storage media, ports(physical and virtual), communication devices, and interfaces capable ofaccessing other clients, servers, machines, and devices through a wiredor a wireless medium, and the like. The methods, programs, or codes asdescribed herein and elsewhere may be executed by the client. Inaddition, other devices required for execution of methods as describedin this application may be considered as a part of the infrastructureassociated with the client.

The client may provide an interface to other devices including, withoutlimitation, servers, other clients, printers, database servers, printservers, file servers, communication servers, distributed servers andthe like. Additionally, this coupling and/or connection may facilitateremote execution of program across the network. The networking of someor all of these devices may facilitate parallel processing of a programor method at one or more location without deviating from the scope ofthe invention. In addition, any of the devices attached to the clientthrough an interface may include at least one storage medium capable ofstoring methods, programs, applications, code and/or instructions. Acentral repository may provide program instructions to be executed ondifferent devices. In this implementation, the remote repository may actas a storage medium for program code, instructions, and programs.

The methods and systems described herein may be deployed in part or inwhole through network infrastructures. The network infrastructure mayinclude elements such as computing devices, servers, routers, hubs,firewalls, clients, personal computers, communication devices, routingdevices and other active and passive devices, modules and/or componentsas known in the art. The computing and/or non-computing device(s)associated with the network infrastructure may include, apart from othercomponents, a storage medium such as flash memory, buffer, stack, RAM,ROM and the like. The processes, methods, program codes, instructionsdescribed herein and elsewhere may be executed by one or more of thenetwork infrastructural elements.

The methods, program codes, and instructions described herein andelsewhere may be implemented on a cellular network having multiplecells. The cellular network may either be frequency division multipleaccess (FDMA) network or code division multiple access (CDMA) network.The cellular network may include mobile devices, cell sites, basestations, repeaters, antennas, towers, and the like. The cell networkmay be a GSM, GPRS, 3G, EVDO, mesh, or other networks types.

The methods, programs codes, and instructions described herein andelsewhere may be implemented on or through mobile devices. The mobiledevices may include navigation devices, cell phones, mobile phones,mobile personal digital assistants, laptops, palmtops, netbooks, pagers,electronic books readers, music players and the like. These devices mayinclude, apart from other components, a storage medium such as a flashmemory, buffer, RAM, ROM and one or more computing devices. Thecomputing devices associated with mobile devices may be enabled toexecute program codes, methods, and instructions stored thereon.Alternatively, the mobile devices may be configured to executeinstructions in collaboration with other devices. The mobile devices maycommunicate with base stations interfaced with servers and configured toexecute program codes. The mobile devices may communicate on apeer-to-peer network, mesh network, or other communications network. Theprogram code may be stored on the storage medium associated with theserver and executed by a computing device embedded within the server.The base station may include a computing device and a storage medium.The storage device may store program codes and instructions executed bythe computing devices associated with the base station.

The computer software, program codes, and/or instructions may be storedand/or accessed on machine readable media that may include: computercomponents, devices, and recording media that retain digital data usedfor computing for some interval of time; semiconductor storage known asrandom access memory (RAM); mass storage typically for more permanentstorage, such as optical discs, forms of magnetic storage like harddisks, tapes, drums, cards and other types; processor registers, cachememory, volatile memory, non-volatile memory; optical storage such asCD, DVD; removable media such as flash memory (e.g. USB sticks or keys),floppy disks, magnetic tape, paper tape, punch cards, standalone RAMdisks, Zip drives, removable mass storage, off-line, and the like; othercomputer memory such as dynamic memory, static memory, read/writestorage, mutable storage, read only, random access, sequential access,location addressable, file addressable, content addressable, networkattached storage, storage area network, bar codes, magnetic ink, and thelike.

The methods and systems described herein may transform physical and/oror intangible items from one state to another. The methods and systemsdescribed herein may also transform data representing physical and/orintangible items from one state to another.

The elements described and depicted herein, including in flow charts andblock diagrams throughout the figures, imply logical boundaries betweenthe elements. However, according to software or hardware engineeringpractices, the depicted elements and the functions thereof may beimplemented on machines through computer executable media having aprocessor capable of executing program instructions stored thereon as amonolithic software structure, as standalone software modules, or asmodules that employ external routines, code, services, and so forth, orany combination of these, and all such implementations may be within thescope of the present disclosure. Examples of such machines may include,but may not be limited to, personal digital assistants, laptops,personal computers, mobile phones, other handheld computing devices,medical equipment, wired or wireless communication devices, transducers,chips, calculators, satellites, tablet PCs, electronic books, gadgets,electronic devices, devices having artificial intelligence, computingdevices, networking equipments, servers, routers and the like.Furthermore, the elements depicted in the flow chart and block diagramsor any other logical component may be implemented on a machine capableof executing program instructions. Thus, while the foregoing drawingsand descriptions set forth functional aspects of the disclosed systems,no particular arrangement of software for implementing these functionalaspects should be inferred from these descriptions unless explicitlystated or otherwise clear from the context. Similarly, it will beappreciated that the various steps identified and described above may bevaried, and that the order of steps may be adapted to particularapplications of the techniques disclosed herein. All such variations andmodifications are intended to fall within the scope of this disclosure.As such, the depiction and/or description of an order for various stepsshould not be understood to require a particular order of execution forthose steps, unless required by a particular application, or explicitlystated or otherwise clear from the context.

The methods and/or processes described above, and steps thereof, may berealized in hardware, software or any combination of hardware andsoftware suitable for a particular application. The hardware may includea general-purpose computer and/or dedicated computing device or specificcomputing device or particular aspect or component of a specificcomputing device. The processes may be realized in one or moremicroprocessors, microcontrollers, embedded microcontrollers,programmable digital signal processors or other programmable device,along with internal and/or external memory. The processes may also, orinstead, be embodied in an application specific integrated circuit, aprogrammable gate array, programmable array logic, or any other deviceor combination of devices that may be configured to process electronicsignals. It will further be appreciated that one or more of theprocesses may be realized as a computer executable code capable of beingexecuted on a machine-readable medium.

The computer executable code may be created using a structuredprogramming language such as C, an object oriented programming languagesuch as C++, or any other high-level or low-level programming language(including assembly languages, hardware description languages, anddatabase programming languages and technologies) that may be stored,compiled or interpreted to run on one of the above devices, as well asheterogeneous combinations of processors, processor architectures, orcombinations of different hardware and software, or any other machinecapable of executing program instructions.

Thus, in one aspect, each method described above and combinationsthereof may be embodied in computer executable code that, when executingon one or more computing devices, performs the steps thereof. In anotheraspect, the methods may be embodied in systems that perform the stepsthereof, and may be distributed across devices in a number of ways, orall of the functionality may be integrated into a dedicated, standalonedevice or other hardware. In another aspect, the means for performingthe steps associated with the processes described above may include anyof the hardware and/or software described above. All such permutationsand combinations are intended to fall within the scope of the presentdisclosure.

While the invention has been disclosed in connection with the preferredembodiments shown and described in detail, various modifications andimprovements thereon will become readily apparent to those skilled inthe art. Accordingly, the spirit and scope of the present invention isnot to be limited by the foregoing examples, but is to be understood inthe broadest sense allowable by law.

All documents referenced herein are hereby incorporated by reference.

What is claimed is:
 1. A method of managing RFID tags, comprising:presenting an RFID tag and associated RFID tag data to a computingdevice through an RFID drive management facility as a seamless extensionof a logical file system within the computing device such that the RFIDtag and associated RFID tag data can be managed in a manner that isconsistent with other items within the file system.
 2. The method ofclaim 1, wherein the RFID tag is mounted as a file system elementaccessible within the local and network file system available to thecomputing device.
 3. The method of claim 2, wherein the file systemelement is at least one of a drive, folder, network share, and uniformresource location.
 4. The method of claim 3, wherein the identity of theRFID tag is changeable by changing the name of the at least one ofdrive, folder, network share, and uniform resource location.
 5. Themethod of claim 1, wherein the RFID drive management facility operatesautonomously and transparently to the user with minimal interaction,such that the user interface for reading and writing data is the same asthe file system.
 6. The method of claim 1, wherein the computer deviceis at least one of a server, a desktop computer, a laptop computer, atablet computing device, and a smart phone.
 7. The method of claim 1,further comprising editing the RFID tag data on the computing device andtransferring the edited RFID tag data to the RFID tag.
 8. The method ofclaim 7, wherein the editing is provided within at least one of theoperating system and a user interface environment.
 9. The method ofclaim 7, wherein the editing is provided by changes to file systemelements by at least one of an application and run time system withinthe computing device.
 10. The method of claim 7, wherein the editingallows an existing application to read and write data to and from tagsthrough its conventional file-handling interface.
 11. The method ofclaim 1, further comprising transferring the RFID tag data from thecomputer device to at least one of a server-based cloud and local areanetwork storage facility, wherein the RFID tag data is made available toa second computer device.
 12. The method of claim 1, wherein the RFIDtag data is stored on the RFID tag in one-time programmable (OTP)memory.
 13. The method of claim 12, wherein the OTP memory is configuredas emulated multiple-time programmable (eMTP) memory.
 14. The method ofclaim 1, wherein the RFID drive management facility provides a mappingof an RFID data format to a computer file format.
 15. The method ofclaim 14, wherein the RFID drive management facility simultaneouslyprovides mapping to a plurality of computer file formats.
 16. The methodof claim 1, wherein the RFID drive management facility identifies anRFID tag data format and assigns a converter to translate and convertbetween the file format within the computer system and the data formatwithin the RFID tag.
 17. The method of claim 1, wherein the RFID drivemanagement facility provides a data format within the RFID tag withadditional processing to convert between the RFID tag data format andthe computing system format.
 18. The method of claim 1, wherein controlfunctionality for the RFID drive management facility is accessed from atleast one of a control and status icon within the user desktop.
 19. Themethod of claim 1, wherein the RFID drive management facility isintegrated with and managed by network management software.
 20. Themethod of claim 1, further comprising an RFID interrogator interfaced tothe RFID drive management facility via a dedicated connection.
 21. Amethod of managing RFID tags, comprising: providing an RFID drivemanagement facility on a computer system, the computer systemcommunicating with an RFID tag and having a logical file system; withthe drive management facility presenting an RFID tag as an extension ofthe logical file system; and with the drive management facilityproviding the ability to manage data on the RFID tag in the logical filesystem.
 22. The method of claim 21, wherein the communication isprovided wirelessly through an RFID interrogator device.
 23. The methodof claim 21, wherein the communication is provided across a network toan RFID interrogator device that wirelessly communicates with the RFIDtag.
 24. The method of claim 21, wherein the RFID tag is mounted as afile system element accessible within the local and network file systemavailable to the computer system.
 25. A computer implemented system ofmanaging RFID tags, comprising: an RFID tag; a memory comprisinginstructions; a processor receiving data from the RFID tag and that,upon executing the instruction, performs the steps of: providing a RFIDdrive management facility on the computer system, the computer systemhaving a logical file system; presenting an RFID tag as an extension ofthe logical file system; providing the ability to manage data on theRFID tag in the logical file system
 26. The method of claim 21, whereinthe receiving of data is provided wirelessly through an RFIDinterrogator device.
 27. The method of claim 21, wherein the receivingof data is provided across a network to an RFID interrogator device thatwirelessly communicates with the RFID tag.
 28. The method of claim 21,wherein the RFID tag is mounted as a file system element accessiblewithin the local and network file system available to the computersystem.